Merge branch 'docs-gitlab-basics-followup' into 'master'

Resolving minor formatting issues in gitlab-basics Closes #65307 See merge request gitlab-org/gitlab-ce!32194

Merge branch 'docs-gitlab-basics-followup' into 'master'
Resolving minor formatting issues in gitlab-basics Closes #65307 See merge request gitlab-org/gitlab-ce!32194
5822c092 · Evan Read · 0b563f87 · 9c6b35e3 · 5822c092 · 5822c092
--- a/doc/gitlab-basics/add-merge-request.md
+++ b/doc/gitlab-basics/add-merge-request.md
@@ -12,8 +12,6 @@ check the [merge requests documentation](../user/project/merge_requests/index.md
 you can watch our [GitLab Flow video](https://www.youtube.com/watch?v=InKNIvky2KE) for
 a quick overview of working with merge requests.

---
-
 1. Before you start, you should have already [created a branch](create-branch.md)
   and [pushed your changes](start-using-git.md#send-changes-to-gitlabcom) to GitLab.
 1. Go to the project where you'd like to merge your changes and click on the

--- a/doc/gitlab-basics/create-project.md
+++ b/doc/gitlab-basics/create-project.md
@@ -2,7 +2,7 @@
 type: howto
 ---

-# Creating projects
+# Create a project

 Most work in GitLab is done within a [Project](../user/project/index.md). Files and
 code are saved in projects, and most features are used within the scope of projects.

--- a/doc/gitlab-basics/create-your-ssh-keys.md
+++ b/doc/gitlab-basics/create-your-ssh-keys.md
@@ -5,7 +5,7 @@ type: howto
 # Create and add your SSH public key

 It is best practice to use [Git over SSH instead of Git over HTTP](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols).
-In order to use SSH, you will need to
+In order to use SSH, you will need to:

 1. [Create an SSH key pair](#creating-your-ssh-key-pair) on your local computer.
 1. [Add the key to GitLab](#adding-your-ssh-public-key-to-gitlab).