Skip to content

fix: correct typos and grammar in migrating_to_ocis docs (#1536)#1537

Merged
phil-davis merged 1 commit into
10.16from
backport/793588c3a20e67338d5aa6f4ba807dc6e5062fac
Jun 12, 2026
Merged

fix: correct typos and grammar in migrating_to_ocis docs (#1536)#1537
phil-davis merged 1 commit into
10.16from
backport/793588c3a20e67338d5aa6f4ba807dc6e5062fac

Conversation

@DeepDiver1975

Copy link
Copy Markdown
Member
  • fix: correct doubled word in "Migration With LDAP Users" docs

The intro of the "Migration With LDAP Users" section had a doubled word ("connected to to a different backend") and a slightly awkward "either connecting ... or by migrating" construction. Reword for clarity and parallel structure.

Reported in owncloud/migrate_to_ocis#30.

  • fix: correct typos and grammar in migrating_to_ocis docs

Fix several language issues found while reviewing the migration guide:

  • "oCis" -> "oCIS" (consistent product capitalization)
  • "how to setup" -> "how to set up" (verb form)
  • "Files of enabled users from in each user's home" -> "Files in each enabled user's home" (broken "from in", redundant phrasing)
  • "the users personal Space" -> "the user's personal Space" (possessive)
  • "IDM - where" -> "IDM — where" (em dash, consistent with rest of doc)
  • "migrating users and groups are divided" -> "the migration of users and groups is divided" (subject/verb clarity)
  • add comma before non-restrictive "which" in the ownCloud schema note

* fix: correct doubled word in "Migration With LDAP Users" docs

The intro of the "Migration With LDAP Users" section had a doubled
word ("connected to to a different backend") and a slightly awkward
"either connecting ... or by migrating" construction. Reword for
clarity and parallel structure.

Reported in owncloud/migrate_to_ocis#30.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>

* fix: correct typos and grammar in migrating_to_ocis docs

Fix several language issues found while reviewing the migration guide:

- "oCis" -> "oCIS" (consistent product capitalization)
- "how to setup" -> "how to set up" (verb form)
- "Files of enabled users from in each user's home" -> "Files in each
  enabled user's home" (broken "from in", redundant phrasing)
- "the users personal Space" -> "the user's personal Space" (possessive)
- "IDM - where" -> "IDM — where" (em dash, consistent with rest of doc)
- "migrating users and groups are divided" -> "the migration of users
  and groups is divided" (subject/verb clarity)
- add comma before non-restrictive "which" in the ownCloud schema note

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>

---------

Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
@DeepDiver1975 DeepDiver1975 requested a review from mmattel June 12, 2026 14:44
@mmattel

mmattel commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Needs porting to master.

@phil-davis

Copy link
Copy Markdown
Contributor

Needs porting to master.

This is a backport of #1536 that was merged to master.

@phil-davis phil-davis merged commit 8d1c1bf into 10.16 Jun 12, 2026
2 checks passed
@phil-davis phil-davis deleted the backport/793588c3a20e67338d5aa6f4ba807dc6e5062fac branch June 12, 2026 16:22
@mmattel

mmattel commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

It would be easier to identify if we would use the convention I implemented for the PR header on backports. That was made intentionally exacly because of this...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants