Edit user contribution and membership mapping docs

doc/user/group/import/direct_transfer_migrations.md

@@ -70,7 +70,7 @@ GitLab 16.8.
   - For [a whole instance](../../../administration/settings/visibility_and_access_controls.md#define-which-roles-can-create-projects).
   - For [specific groups](../index.md#specify-who-can-add-projects-to-a-group).
 
-## User contributions and membership mapping
+## User contribution and membership mapping
 
 DETAILS:
 **Offering:** Self-managed, GitLab Dedicated
@@ -80,11 +80,11 @@ DETAILS:
 > - Full support for mapping inherited membership [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/458834) in GitLab 17.1.
 > - Removed from GitLab.com direct transfer migrations in GitLab 17.5 in favor of [the alternative](../../project/import/index.md#user-contribution-and-membership-mapping).
 
-This method of user contributions and membership mapping is available for
+This method of user contribution and membership mapping is available for
 GitLab self-managed without enabled feature flags.
 For information on the other method available for GitLab self-managed
 with enabled feature flags and for GitLab.com,
-see [User contribution and membership mapping](../../project/import/index.md#user-contribution-and-membership-mapping).
+see [user contribution and membership mapping](../../project/import/index.md#user-contribution-and-membership-mapping).
 
 Users are never created during a migration. Instead, contributions and membership of users on the source instance are
 mapped to users on the destination instance. The type of mapping of a user's membership depends on the

doc/user/group/import/migrated_items.md

@@ -53,13 +53,13 @@ Group items that are migrated to the destination GitLab instance include:
 
 **Footnotes:**
 
-1. Epic resource state events [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/291983) in GitLab 15.4, label
-   associations [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/62074) in GitLab 13.12, state and
-   state ID [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28203) in GitLab 13.7, and system note
-   metadata [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63551) in GitLab 14.0.
-1. Group Labels cannot retain any associated Label Priorities during import. These labels will need to be re-prioritized manually
-   once the relevant Project is migrated to the destination instance.
-1. See [User contributions and membership mapping](direct_transfer_migrations.md#user-contributions-and-membership-mapping).
+1. State and state ID [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28203) in GitLab 13.7.
+   Label associations [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/62074) in GitLab 13.12.
+   System note metadata [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63551) in GitLab 14.0.
+   Epic resource state events [introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/291983) in GitLab 15.4.
+1. Group labels cannot retain any associated label priorities during import.
+   You must prioritize these labels again manually after you migrate the relevant project to the destination instance.
+1. See [user contribution and membership mapping](direct_transfer_migrations.md#user-contribution-and-membership-mapping).
 
 <!-- vale gitlab_base.OutdatedVersions = YES -->
 
@@ -143,9 +143,9 @@ Project items that are migrated to the destination GitLab instance include:
 
 **Footnotes:**
 
-1. Imported branches respect the [default branch protection settings](../../project/repository/branches/protected.md)
-   of the destination group, which could cause an unprotected branch to be imported as protected.
-1. See [User contributions and membership mapping](direct_transfer_migrations.md#user-contributions-and-membership-mapping).
+1. Imported branches respect the [default branch protection settings](../../project/repository/branches/protected.md) of the destination group.
+   These settings might cause an unprotected branch to be imported as protected.
+1. See [user contribution and membership mapping](direct_transfer_migrations.md#user-contribution-and-membership-mapping).
 
 ### Issue-related items
 

doc/user/project/import/gitea.md

@@ -100,4 +100,4 @@ This method of user contribution mapping is available for GitLab self-managed wi
 
 For information on the other method available for GitLab self-managed
 with enabled feature flags and for GitLab.com,
-see [User contribution and membership mapping](../../project/import/index.md#user-contribution-and-membership-mapping).
+see [user contribution and membership mapping](../../project/import/index.md#user-contribution-and-membership-mapping).

doc/user/project/import/index.md

@@ -97,14 +97,14 @@ For more information, see the history.
 NOTE:
 To leave feedback about this feature, add a comment to [issue 502565](https://gitlab.com/gitlab-org/gitlab/-/issues/502565).
 
-This method of user contributions and membership mapping is available for
+This method of user contribution and membership mapping is available for
 [direct transfer migrations](../../group/import/index.md) on:
 
 - GitLab.com
 - GitLab self-managed when two feature flags are enabled
 
 For information on the other method available for GitLab self-managed without enabled feature flags,
-see [User contributions and membership mapping](../../group/import/direct_transfer_migrations.md#user-contributions-and-membership-mapping).
+see [user contribution and membership mapping](../../group/import/direct_transfer_migrations.md#user-contribution-and-membership-mapping).
 
 With user contribution and membership mapping, you can assign imported contributions and memberships to users on the
 destination instance after import has completed. Unlike the previous method of user contribution and membership mapping,