maintain uniform styling of GitLab

add suggestion for GitLab instance recommendation

Author: Xronophobe

chapter_25_CI.asciidoc

@@ -122,6 +122,9 @@ They just don't need any _more_ help dominating the market.
 // DAVID: 1e / 2e abbreviations might confuse people.
 
 So I've decided to use GitLab in this book.
+// CSANAD: I just found framagit.org by Framasoft. Maybe we could mention them? Although
+// it might be important to ask them first, in case they need to handle the
+// expected additional traffic.
 They are absolutely a commercial service,
 but they retain an open-source version, and you can self-host it in theory.
 
@@ -150,7 +153,7 @@ so the first thing to do is get our code up there.
 Use the **New Project** -> **Create Blank Project** option, as in <<gitlab-new-blank-project>>.
 
 //RITA: The screenshot shows that the project name and slug are "Superlistz", yet the next figure  that shows the CI project files on GitLab refers to "lists". Is this correct?
-.Creating a New Repo on Gitlab
+.Creating a New Repo on GitLab
 [[gitlab-new-blank-project]]
 image::images/gitlab_new_blank_project.png["New Blank Project"]
 
@@ -961,7 +964,7 @@ test:
 
 
 In any case that should work.
-If you commit the code and then push it back to Gitlab,
+If you commit the code and then push it back to GitLab,
 we should be able to see a new build job.
 
 [role="dofirst-ch25l010-1"]