Merge branch 'docs-fix-gitlab-capitalization-ce-ee' into 'master'

Correcting Gitlab to GitLab in docs (Port to EE)

See merge request gitlab-org/gitlab-ee!7423

doc/administration/geo/disaster_recovery/background_verification.md

@@ -2,7 +2,7 @@
 
 NOTE: **Note:**
 Automatic background verification of repositories and wikis was added in
-GitLab EE 10.6 but is enabled by default only on Gitlab EE 11.1. You can
+GitLab EE 10.6 but is enabled by default only on GitLab EE 11.1. You can
 disable or enable this feature manually by following
 [these instructions][feature-flag].
 

doc/administration/gitaly/index.md

@@ -219,7 +219,7 @@ repository from your GitLab server over HTTP.
 
 If you are running Gitaly [as a remote
 service](#running-gitaly-on-its-own-server) you may want to disable
-the local Gitaly service that runs on your Gitlab server by default.
+the local Gitaly service that runs on your GitLab server by default.
 
 > 'Disabling Gitaly' only makes sense when you run GitLab in a custom
 cluster configuration, where different services run on different

doc/administration/high_availability/database.md

@@ -612,7 +612,7 @@ consul['configuration'] = {
 }
 ```
 
-[Reconfigure Omnibus GitLab][reconfigure Gitlab] for the changes to take effect.
+[Reconfigure Omnibus GitLab][reconfigure GitLab] for the changes to take effect.
 
 ##### Example recommended setup for PostgreSQL servers
 
@@ -648,7 +648,7 @@ consul['configuration'] = {
 }
 ```
 
-[Reconfigure Omnibus GitLab][reconfigure Gitlab] for the changes to take effect.
+[Reconfigure Omnibus GitLab][reconfigure GitLab] for the changes to take effect.
 
 ###### Secondary nodes
 
@@ -661,7 +661,7 @@ configuration
 repmgr['master_on_initialization'] = false
 ```
 
-[Reconfigure Omnibus GitLab][reconfigure Gitlab] for the changes to take effect.
+[Reconfigure Omnibus GitLab][reconfigure GitLab] for the changes to take effect.
 
 ##### Example recommended setup for application server
 
@@ -699,7 +699,7 @@ consul['configuration'] = {
 }
 ```
 
-[Reconfigure Omnibus GitLab][reconfigure Gitlab] for the changes to take effect.
+[Reconfigure Omnibus GitLab][reconfigure GitLab] for the changes to take effect.
 
 ##### Example recommended setup manual steps
 
@@ -803,7 +803,7 @@ consul['configuration'] = {
 }
 ```
 
-[Reconfigure Omnibus GitLab][reconfigure Gitlab] for the changes to take effect.
+[Reconfigure Omnibus GitLab][reconfigure GitLab] for the changes to take effect.
 
 ###### Secondary nodes
 
@@ -851,7 +851,7 @@ consul['configuration'] = {
 }
 ```
 
-[Reconfigure Omnibus GitLab][reconfigure Gitlab] for the changes to take effect.
+[Reconfigure Omnibus GitLab][reconfigure GitLab] for the changes to take effect.
 
 ##### Example minimal setup manual steps
 

doc/administration/high_availability/nfs_host_client_setup.md

@@ -99,7 +99,7 @@ We recommend using version 4 and do not specifically test NFSv3.
 ```
 Reboot the client and confirm that the mount point is mounted automatically.
 
-#### Step 4 - Set up Gitlab to Use NFS mounts
+#### Step 4 - Set up GitLab to Use NFS mounts
 
 When using the default Omnibus configuration you will need to share 5 data locations
 between all GitLab cluster nodes. No other locations should be shared. Changing the

doc/administration/logs.md

@@ -13,7 +13,7 @@ This guide talks about how to read and use these system log files.
 
 This file lives in `/var/log/gitlab/gitlab-rails/production_json.log` for
 Omnibus GitLab packages or in `/home/git/gitlab/log/production_json.log` for
-installations from source. (When Gitlab is running in an environment
+installations from source. (When GitLab is running in an environment
 other than production, the corresponding logfile is shown here.)
 
 It contains a structured log for Rails controller requests received from
@@ -42,7 +42,7 @@ In addition, the log contains the IP address from which the request originated
 
 This file lives in `/var/log/gitlab/gitlab-rails/production.log` for
 Omnibus GitLab packages or in `/home/git/gitlab/log/production.log` for
-installations from source. (When Gitlab is running in an environment
+installations from source. (When GitLab is running in an environment
 other than production, the corresponding logfile is shown here.)
 
 It contains information about all performed requests. You can see the
@@ -187,7 +187,7 @@ This file lives in `/var/log/gitlab/gitlab-shell/gitlab-shell.log` for
 Omnibus GitLab packages or in `/home/git/gitlab-shell/gitlab-shell.log` for
 installations from source.
 
-GitLab shell is used by Gitlab for executing Git commands and provide
+GitLab shell is used by GitLab for executing Git commands and provide
 SSH access to Git repositories. For example:
 
 ```

doc/administration/raketasks/maintenance.md

@@ -58,9 +58,9 @@ Runs the following rake tasks:
 
 It will check that each component was set up according to the installation guide and suggest fixes for issues found.
 
-You may also have a look at our Trouble Shooting Guides:
-- [Trouble Shooting Guide (GitLab)](http://docs.gitlab.com/ee/README.html#troubleshooting)
-- [Trouble Shooting Guide (Omnibus Gitlab)](http://docs.gitlab.com/omnibus/README.html#troubleshooting)
+You may also have a look at our Troubleshooting Guides:
+- [Troubleshooting Guide (GitLab)](http://docs.gitlab.com/ee/README.html#troubleshooting)
+- [Troubleshooting Guide (Omnibus Gitlab)](http://docs.gitlab.com/omnibus/README.html#troubleshooting)
 
 **Omnibus Installation**
 

doc/api/oauth2.md

 # GitLab as an OAuth2 provider
 
-This document covers using the [OAuth2](https://oauth.net/2/) protocol to allow other services access Gitlab resources on user's behalf. 
+This document covers using the [OAuth2](https://oauth.net/2/) protocol to allow other services access GitLab resources on user's behalf. 
 
 If you want GitLab to be an OAuth authentication service provider to sign into other services please see the [OAuth2 provider](../integration/oauth_provider.md)
 documentation.
@@ -9,7 +9,7 @@ This functionality is based on [doorkeeper gem](https://github.com/doorkeeper-ge
 
 ## Supported OAuth2 Flows
 
-Gitlab currently supports following authorization flows: 
+GitLab currently supports following authorization flows: 
 
 * *Web Application Flow* - Most secure and common type of flow, designed for the applications with secure server-side.
 * *Implicit Flow* - This flow is designed for user-agent only apps (e.g. single page web application running on GitLab Pages).
@@ -76,7 +76,7 @@ Check [RFC spec](http://tools.ietf.org/html/rfc6749#section-4.2) for a detailed
 Unlike the web flow, the client receives an `access token` immediately as a result of the authorization request. The flow does not use client secret 
 or authorization code because all of the application code and storage is easily accessible, therefore __secrets__ can leak easily. 
 
->**Important:** Avoid using this flow for applications that store data outside of the Gitlab instance. If you do, make sure to verify `application id` 
+>**Important:** Avoid using this flow for applications that store data outside of the GitLab instance. If you do, make sure to verify `application id` 
 associated with access token before granting access to the data 
 (see [/oauth/token/info](https://github.com/doorkeeper-gem/doorkeeper/wiki/API-endpoint-descriptions-and-examples#get----oauthtokeninfo)). 
  
@@ -146,7 +146,7 @@ access_token = client.password.get_token('user@example.com', 'secret')
 puts access_token.token
 ```
 
-##  Access Gitlab API with `access token`
+##  Access GitLab API with `access token`
 
 The `access token` allows you to make requests to the API on a behalf of a user. You can pass the token either as GET parameter 
 ```

doc/api/services.md

@@ -1153,7 +1153,7 @@ PUT /projects/:id/services/jenkins-deprecated
 Parameters:
 
 - `project_url` (**required**) - Jenkins project URL like http://jenkins.example.com/job/my-project/
-- `multiproject_enabled` (optional) - Multi-project mode is configured in Jenkins Gitlab Hook plugin
+- `multiproject_enabled` (optional) - Multi-project mode is configured in Jenkins GitLab Hook plugin
 - `pass_unstable` (optional) - Unstable builds will be treated as passing
 
 ### Delete Jenkins CI (Deprecated) service

doc/ci/examples/test-scala-application.md

 # Test and deploy to Heroku a Scala application
 
-This example demonstrates the integration of Gitlab CI with Scala
+This example demonstrates the integration of GitLab CI with Scala
 applications using SBT. Checkout the example
 [project](https://gitlab.com/gitlab-examples/scala-sbt) and
 [build status](https://gitlab.com/gitlab-examples/scala-sbt/builds).

doc/ci/yaml/README.md

@@ -188,7 +188,7 @@ used for time of the job. The configuration of this feature is covered in
 
 ## `before_script` and `after_script`
 
-> Introduced in GitLab 8.7 and requires Gitlab Runner v1.2
+> Introduced in GitLab 8.7 and requires GitLab Runner v1.2
 
 `before_script` is used to define the command that should be run before all
 jobs, including deploy jobs, but after the restoration of [artifacts](#artifacts).

doc/development/gitaly.md

@@ -9,7 +9,7 @@ status of the migration.
 
 ## Developing new Git features
 
-Starting with Gitlab 10.8, all new Git features should be developed in
+Starting with GitLab 10.8, all new Git features should be developed in
 Gitaly.
 
 > This is a new process that is not clearly defined yet. If you want

doc/development/ux_guide/users.md

@@ -242,7 +242,7 @@ Some of GitLab EE's features are too basic, in particular, issues boards which d
 James and his team use CI quite heavily for several projects. Whilst they've welcomed improvements to the builds and pipelines interface, they still have some difficulty following build process on the different tabs under Pipelines. Some confusion has arisen from not knowing where to find different pieces of information or how to get to the next stages logs from the current stage's log output screen. They feel more intuitive linking and flow may alleviate the problem. Generally, they feel GitLab's navigation needs to reviewed and optimized.
 
 #### Permissions
->"There is no granular control over user or group permissions. The permissions for a project are too tightly coupled to the permissions for Gitlab CI/build pipelines."
+>"There is no granular control over user or group permissions. The permissions for a project are too tightly coupled to the permissions for GitLab CI/build pipelines."
 
 
 ### Goals
@@ -290,7 +290,7 @@ JavaScript and SQL
 Web development, mobile development, UX, open source, gaming, and travel.
 
 ### Motivations
-Karolina has been using GitLab.com for around a year. She roughly spends 8 hours every week programming, of that, 2 hours is spent contributing to open source projects. Karolina contributes to open source projects to gain programming experience and to give back to the community. She likes GitLab.com for its free private repositories and range of features which provide her with everything she needs for her personal projects. Karolina is also a massive fan of GitLab's values and the fact that it isn't a "behemoth of a company".  She explains that "displaying every single thing (doc, culture, assumptions, development...) in the open gives me greater confidence to choose Gitlab personally and to recommend it at work."  She's also an avid reader of GitLab's blog.
+Karolina has been using GitLab.com for around a year. She roughly spends 8 hours every week programming, of that, 2 hours is spent contributing to open source projects. Karolina contributes to open source projects to gain programming experience and to give back to the community. She likes GitLab.com for its free private repositories and range of features which provide her with everything she needs for her personal projects. Karolina is also a massive fan of GitLab's values and the fact that it isn't a "behemoth of a company".  She explains that "displaying every single thing (doc, culture, assumptions, development...) in the open gives me greater confidence to choose GitLab personally and to recommend it at work."  She's also an avid reader of GitLab's blog.
 
 Karolina works for a software development company which currently hires around 500 people. Karolina would love to use GitLab at work but the company has used GitHub Enterprise for a number of years. She describes management at her company as "old fashioned" and explains that it's "less of a technical issue and more of a cultural issue" to convince upper management to move to GitLab. Karolina is also relatively new to the company so she's apprehensive about pushing too hard to change version control platforms.
 

doc/gitlab-basics/add-image.md

@@ -5,7 +5,7 @@ in Windows, or...), put the image file into the GitLab project. You can find the
 project as a regular folder in your files.
 
 Go to your [shell](command-line-commands.md), and move into the folder of your
-Gitlab project. This usually means running the following command until you get
+GitLab project. This usually means running the following command until you get
 to the desired destination:
 
 ```

doc/install/kubernetes/gitlab_chart.md

@@ -93,7 +93,7 @@ You can access the GitLab instance by visiting the domain name beginning with
 above, the URL would be `https://gitlab.example.com`.
 
 If you manually created the secret for initial root password, you
-can use that to sign in as `root` user. If not, Gitlab automatically
+can use that to sign in as `root` user. If not, GitLab automatically
 created a random password for `root` user. This can be extracted by the
 following command (replace `<name>` by name of the release - which is `gitlab`
 if you used the command above):

doc/integration/github.md

@@ -19,7 +19,7 @@ GitHub will generate an application ID and secret key for you to use.
     - Application name: This can be anything. Consider something like `<Organization>'s GitLab` or `<Your Name>'s GitLab` or something else descriptive.
     - Homepage URL: The URL to your GitLab installation. 'https://gitlab.company.com'
     - Application description: Fill this in if you wish.
-    - Authorization callback URL is 'http(s)://${YOUR_DOMAIN}'. Please make sure the port is included if your Gitlab instance is not configured on default port.
+    - Authorization callback URL is 'http(s)://${YOUR_DOMAIN}'. Please make sure the port is included if your GitLab instance is not configured on default port.
 1.  Select "Register application".
 
 1.  You should now see a Client ID and Client Secret near the top right of the page (see screenshot).
@@ -154,7 +154,7 @@ You will also need to disable Git SSL verification on the server hosting GitLab.
 $ git config --global http.sslVerify false
 ```
 
-For the changes to take effect, [reconfigure Gitlab] if you installed
+For the changes to take effect, [reconfigure GitLab] if you installed
 via Omnibus, or [restart GitLab] if you installed from source.
 
 [reconfigure GitLab]: ../administration/restart_gitlab.md#omnibus-gitlab-reconfigure

doc/security/user_email_confirmation.md

 # User email confirmation at sign-up
 
-Gitlab admin can enable email confirmation on sign-up, if you want to confirm all
+GitLab admin can enable email confirmation on sign-up, if you want to confirm all
 user emails before they are able to sign-in.
 
 In the Admin area under **Settings** (`/admin/application_settings`), go to section

doc/university/README.md

@@ -11,7 +11,7 @@ and [Blog Articles](https://about.gitlab.com/blog/).
 
 Would you like to contribute to GitLab University? Then please take a look at our contribution [process](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md) for more information.
 
-## Gitlab University Curriculum
+## GitLab University Curriculum
 
 The curriculum is composed of GitLab videos, screencasts, presentations, projects and external GitLab content hosted on other services and has been organized into the following sections.
 

doc/user/admin_area/settings/visibility_and_access_controls.md

@@ -44,7 +44,7 @@ application level.
 
 ## Allow mirrors to be set up for projects
 
-> [Introduced][ee-3586] in Gitlab 10.3.
+> [Introduced][ee-3586] in GitLab 10.3.
 
 This option is enabled by default. By disabling it, both pull and push mirroring will no longer
 work in every repository and can only be re-enabled on a per-project basis by an admin.

doc/user/gitlab_com/index.md

@@ -221,7 +221,7 @@ and the following environment variables:
 
 ## Cron jobs
 
-Periodically executed jobs by Sidekiq, to self-heal Gitlab, do external
+Periodically executed jobs by Sidekiq, to self-heal GitLab, do external
 synchronizations, run scheduled pipelines, etc.:
 
 | Setting                     | GitLab.com   | Default      |

doc/user/index.md

@@ -97,7 +97,7 @@ directly from GitLab. No third-party integrations needed.
 - [GitLab Auto Deploy](../ci/autodeploy/index.md): Deploy your application out-of-the-box with GitLab Auto Deploy.
 - [Review Apps](../ci/review_apps/index.md): Live-preview the changes introduced by a merge request with Review Apps.
 - [GitLab Pages](project/pages/index.md): Publish your static site directly from
-GitLab with Gitlab Pages. You can build, test, and deploy any Static Site Generator with Pages.
+GitLab with GitLab Pages. You can build, test, and deploy any Static Site Generator with Pages.
 - [GitLab Container Registry](project/container_registry.md): Build and deploy Docker
 images with Container Registry.
 

doc/user/project/integrations/webhooks.md

@@ -1195,7 +1195,7 @@ You can trigger the webhook manually. Sample data from the project will be used.
 
 ## Troubleshoot webhooks
 
-Gitlab stores each perform of the webhook.
+GitLab stores each perform of the webhook.
 You can find records for last 2 days in "Recent Deliveries" section on the edit page of each webhook.
 
 ![Recent deliveries](img/webhook_logs.png)