Changing docs based on suggestionsupdate-migration-docs

1 files changed, 8 insertions, 5 deletions

diff --git a/doc/user/project/import/index.md b/doc/user/project/import/index.md
index 84b3d89af88..cc73ea95f51 100644
--- a/doc/user/project/import/index.md
+++ b/doc/user/project/import/index.md
@@ -25,8 +25,10 @@ If you only need to migrate git repos, you can [import each project by URL](repo
 If you want to retain all metadata like issues and merge requests, you can use
 the [import/export feature](../settings/import_export.md) to export projects from self-hosted GitLab and import those projects into GitLab.com.
 
-NOTE: This approach assumes all users from the self-hosted instance have already been migrated. 
-If the users haven't been migrated, the user conducting the import will take the place of all references to the missing user(s)
+NOTE: **Note:**
+This approach assumes all users from the self-hosted instance have already been migrated.
+If the users haven't been migrated yet, the user conducting the import
+will take the place of all references to the missing user(s).
 
 If you need to migrate all data over, you can leverage our [api](../../../api/README.md) to migrate from self-hosted to GitLab.com. 
 The order of assets to migrate from a self-hosted instance to GitLab is the following:
@@ -36,9 +38,10 @@ The order of assets to migrate from a self-hosted instance to GitLab is the foll
 1. [Projects](../../../api/projects.md)
 1. [Project variables](../../../api/project_level_variables.md)
 
-Keep in mind the limitations of our [import/export feature](../settings/import_export.md#exported-contents)
+Keep in mind the limitations of the [import/export feature](../settings/import_export.md#exported-contents).
 
-You will still need to migrate your container registry over a series of docker pulls and pushes and re-run any CI pipelines to retrieve any build artifacts.
+You will still need to migrate your Container Registry over a series of
+Docker pulls and pushes and re-run any CI pipelines to retrieve any build artifacts.
 
 ## Migrating between two self-hosted GitLab instances
 
@@ -48,4 +51,4 @@ perhaps from an old server to a new server for example, is to
 then restore it on the new server.
 
 In the event of merging two GitLab instances together (for example, both instances have existing data on them and one can't be wiped), 
-refer to the instructions in [Migrating from self-hosted GitLab to GitLab.com](#migrating-from-self-hosted-gitlab-to-gitlabcom)
+refer to the instructions in [Migrating from self-hosted GitLab to GitLab.com](#migrating-from-self-hosted-gitlab-to-gitlabcom).