Correct grammar (setup to set-up) in Docs

doc/development/database_debugging.md

@@ -33,7 +33,7 @@ If your test DB is giving you problems, it is safe to nuke it because it doesn't
  - `bundle exec rake db:migrate RAILS_ENV=development`: Execute any pending migrations that you may have picked up from a MR
  - `bundle exec rake db:migrate:status RAILS_ENV=development`: Check if all migrations are `up` or `down`
  - `bundle exec rake db:migrate:down VERSION=20170926203418 RAILS_ENV=development`: Tear down a migration
- - `bundle exec rake db:migrate:up VERSION=20170926203418 RAILS_ENV=development`: Setup a migration
+ - `bundle exec rake db:migrate:up VERSION=20170926203418 RAILS_ENV=development`: Set up a migration
  - `bundle exec rake db:migrate:redo VERSION=20170926203418 RAILS_ENV=development`: Re-run a specific migration

doc/development/module_with_instance_variables.md

@@ -60,7 +60,7 @@ as long as it's contained in the same module; that is, no other modules or
 objects are touching them, then it would be an acceptable use.
 We especially allow the case where a single instance variable is used with
-`||=` to setup the value. This would look like:
+`||=` to set up the value. This would look like:
 ``` ruby
 module M

doc/development/rake_tasks.md

 # Rake tasks for developers
-## Setup db with developer seeds
+## Set up db with developer seeds
 Note that if your db user does not have advanced privileges you must create the db manually before running this command.

doc/development/ux_guide/users.md

@@ -154,7 +154,7 @@ He credits himself as being entirely responsible for moving his company to GitLa
 #### Updating to the latest release
 Matthieu introduced his company to GitLab. He is responsible for maintaining and managing the company's installation in addition to his day job. He feels updates are too frequent and he doesn't always have sufficient time to update GitLab. As a result, he's not up to date with releases. 
-Matthieu tried to set up automatic updates, however, as he isn't a Systems Administrator, he wasn't confident in his set-up. He feels he should be able to "upgrade without users even noticing" but hasn't figured out how to do this yet. Matthieu would like the "update process to be triggered from the Admin Panel, perhaps accompanied with a changelog and the option to skip updates."
+Matthieu tried to set up automatic updates, however, as he isn't a Systems Administrator, he wasn't confident in his setup. He feels he should be able to "upgrade without users even noticing" but hasn't figured out how to do this yet. Matthieu would like the "update process to be triggered from the Admin Panel, perhaps accompanied with a changelog and the option to skip updates."
 Matthieu is looking for confirmation that his update procedure is "secure and efficient" so more tutorials related to this topic would be useful to him.

doc/install/azure/index.md

@@ -74,7 +74,7 @@ The first items we need to configure are the basic settings of the underlying vi
     > **Note:** if you're unsure which authentication type to use, select **Password**
     1. If you chose **SSH public key** - enter your `SSH public key` into the field provided 
-    _(read the [SSH documentation][GitLab-Docs-SSH] to learn more about how to setup SSH 
+    _(read the [SSH documentation][GitLab-Docs-SSH] to learn more about how to set up SSH 
     public keys)_
     1. If you chose **Password** - enter the password you wish to use _(this is the password that you 
     will use later in this tutorial to [SSH] into the VM, so make sure it's a strong password/passphrase)_
@@ -154,7 +154,7 @@ on the Azure Dashboard (you may need to refresh the page):
 The new VM can also be accessed by clicking the `All resources` or `Virtual machines` icons in the 
 Azure Portal sidebar navigation menu.
-## Setup a domain name
+## Set up a domain name
 The VM will have a public IP address (static by default), but Azure allows us to assign a friendly 
 DNS name to the VM, so let's go ahead and do that.
@@ -296,7 +296,7 @@ homepage for the project:
 ![GitLab - Empty Project](img/gitlab-project-home-empty.png)
 If you scroll further down the project's home page, you'll see some basic instructions on how to 
-setup a local clone of your new repository and push and pull from it:
+set up a local clone of your new repository and push and pull from it:
 ![GitLab - Empty Project - Basic Instructions](img/gitlab-project-home-instructions.png)
@@ -347,7 +347,7 @@ If you're running [SSH] from the command-line (terminal), then type in the follo
 connect to your VM, substituting `username` and `your-azure-domain-name.com` for the correct values. 
 Again, remember that your Azure VM domain name will be the one you 
-[setup previously in the tutorial](#set-up-a-domain-name). If you didn't setup a domain name for 
+[set up previously in the tutorial](#set-up-a-domain-name). If you didn't set up a domain name for 
 your VM, you can use the IP address in its place in the following command:
 ```bash
@@ -401,7 +401,7 @@ is now showing **"up-to-date"**:
 Naturally, we believe that GitLab is a great git repository tool. However, GitLab is a whole lot 
 more than that too. GitLab unifies issues, code review, CI and CD into a single UI, helping you to 
 move faster from idea to production, and in this tutorial we showed you how quick and easy it is to 
-setup and run your own instance of GitLab on Azure, Microsoft's cloud service. 
+set up and run your own instance of GitLab on Azure, Microsoft's cloud service. 
 Azure is a great way to experiment with GitLab, and if you decide (as we hope) that GitLab is for 
 you, you can continue to use Azure as your secure, scalable cloud provider or of course run GitLab
@@ -424,7 +424,7 @@ Check out our other [Technical Articles][GitLab-Technical-Articles] or browse th
     - [Azure - Properly Shutdown an Azure VM][Azure-Properly-Shutdown-VM]
 - [SSH], [PuTTY] and [Using SSH in PuTTY][Using-SSH-In-Putty]
-[Original-Blog-Post]: https://about.gitlab.com/2016/07/13/how-to-setup-a-gitlab-instance-on-microsoft-azure/ "How to Setup a GitLab Instance on Microsoft Azure"
+[Original-Blog-Post]: https://about.gitlab.com/2016/07/13/how-to-setup-a-gitlab-instance-on-microsoft-azure/ "How to Set up a GitLab Instance on Microsoft Azure"
 [GitLab-Docs]: https://docs.gitlab.com/ce/README.html "GitLab Documentation"
 [GitLab-Technical-Articles]: https://docs.gitlab.com/ce/articles/index.html "GitLab Technical Articles"
 [GitLab-Docs-SSH]: https://docs.gitlab.com/ce/ssh/README.html "GitLab Documentation: SSH"

doc/install/database_mysql.md

@@ -79,7 +79,7 @@ After installation or upgrade, remember to [convert any new tables](#tables-and-
 ---
-GitLab 8.14 has introduced [a feature](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7420) requiring `utf8mb4` encoding to be supported in your GitLab MySQL Database, which is not the case if you have setup your database before GitLab 8.16.
+GitLab 8.14 has introduced [a feature](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7420) requiring `utf8mb4` encoding to be supported in your GitLab MySQL Database, which is not the case if you have set up your database before GitLab 8.16.
 Follow the below instructions to ensure you use the most up to date requirements for your GitLab MySQL Database.

doc/install/digitaloceandocker.md

@@ -87,7 +87,7 @@ You can add this to your `~/.bash_profile` file to ensure the `docker` client us
 + Container name: `gitlab-test-8.10`
 + GitLab version: **EE** `8.10.8-ee.0`
-#####  Setup container settings
+#####  Set up container settings
 ```
 export SSH_PORT=2222

doc/install/installation.md

@@ -515,7 +515,7 @@ Make GitLab start on boot:
     sudo update-rc.d gitlab defaults 21
-### Setup Logrotate
+### Set up Logrotate
     sudo cp lib/support/logrotate/gitlab /etc/logrotate.d/gitlab

doc/install/openshift_and_gitlab/index.md

@@ -80,7 +80,7 @@ This will download the VirtualBox image and fire up the VM with some preconfigur
 values as you can see in the Vagrantfile. As you may have noticed, you need
 plenty of RAM (5GB in our example), so make sure you have enough.
-Now that OpenShift is setup, let's see how the web console looks like.
+Now that OpenShift is set up, let's see how the web console looks like.
 ### Explore the OpenShift web console

doc/install/relative_url.md

@@ -124,5 +124,5 @@ To disable the relative URL:
 1.  Follow the same as above starting from 2. and set up the
     GitLab URL to one that doesn't contain a relative path.
-[omnibus-rel]: http://docs.gitlab.com/omnibus/settings/configuration.html#configuring-a-relative-url-for-gitlab "How to setup relative URL in Omnibus GitLab"
+[omnibus-rel]: http://docs.gitlab.com/omnibus/settings/configuration.html#configuring-a-relative-url-for-gitlab "How to set up relative URL in Omnibus GitLab"
 [restart gitlab]: ../administration/restart_gitlab.md#installations-from-source "How to restart GitLab"

doc/integration/gmail_action_buttons_for_gitlab.md

@@ -2,7 +2,7 @@
 GitLab supports [Google actions in email](https://developers.google.com/gmail/markup/actions/actions-overview).
-If correctly setup, emails that require an action will be marked in Gmail.
+If correctly set up, emails that require an action will be marked in Gmail.
 ![gmail_actions_button.png](img/gmail_action_buttons_for_gitlab.png)

doc/security/two_factor_authentication.md

@@ -11,7 +11,7 @@ You can read more about it here:
 ## Enforcing 2FA for all users
 Users on GitLab, can enable it without any admin's intervention. If you want to
-enforce everyone to setup 2FA, you can choose from two different ways:
+enforce everyone to set up 2FA, you can choose from two different ways:
  1. Enforce on next login
  2. Suggest on next login, but allow a grace period before enforcing.

doc/topics/authentication/index.md

@@ -44,6 +44,6 @@ This page gathers all the resources for the topic **Authentication** within GitL
 - [Kanboard Plugin GitLab Authentication](https://kanboard.net/plugin/gitlab-auth)
 - [Jenkins GitLab OAuth Plugin](https://wiki.jenkins-ci.org/display/JENKINS/GitLab+OAuth+Plugin)
-- [Setup Gitlab CE with Active Directory authentication](https://www.caseylabs.com/setup-gitlab-ce-with-active-directory-authentication/)
+- [Set up Gitlab CE with Active Directory authentication](https://www.caseylabs.com/setup-gitlab-ce-with-active-directory-authentication/)
 - [How to customize GitLab to support OpenID authentication](http://eric.van-der-vlist.com/blog/2013/11/23/how-to-customize-gitlab-to-support-openid-authentication/)
 - [Openshift - Configuring Authentication and User Agent](https://docs.openshift.org/latest/install_config/configuring_authentication.html#GitLab)

doc/university/glossary/README.md

@@ -395,7 +395,7 @@ Allow you to [organize issues](../../user/project/milestones/index.md) and merge
 ### Mirror Repositories
-A project that is setup to automatically have its branches, tags, and commits [updated from an upstream repository](https://docs.gitlab.com/ee/workflow/repository_mirroring.html). This is useful when a repository you're interested in is located on a different server, and you want to be able to browse its content and activity using the familiar GitLab interface.
+A project that is set up to automatically have its branches, tags, and commits [updated from an upstream repository](https://docs.gitlab.com/ee/workflow/repository_mirroring.html). This is useful when a repository you're interested in is located on a different server, and you want to be able to browse its content and activity using the familiar GitLab interface.
 ### MIT License
@@ -673,7 +673,7 @@ Version control is a system that records changes to a file or set of files over
 ### Virtual Private Cloud (VPC)
-A [VPC](https://docs.gitlab.com/ce/university/glossary/README.html#virtual-private-cloud-vpc) is an on demand configurable pool of shared computing resources allocated within a public cloud environment, providing some isolation between the different users using the resources. GitLab users need to create a new Amazon VPC in order to [setup High Availability](https://docs.gitlab.com/ce/university/high-availability/aws/).
+A [VPC](https://docs.gitlab.com/ce/university/glossary/README.html#virtual-private-cloud-vpc) is an on demand configurable pool of shared computing resources allocated within a public cloud environment, providing some isolation between the different users using the resources. GitLab users need to create a new Amazon VPC in order to [set up High Availability](https://docs.gitlab.com/ce/university/high-availability/aws/).
 ### Virtual private server (VPS)

doc/university/high-availability/aws/README.md

@@ -286,7 +286,7 @@ to make the EFS integration easier to manage.
     gitlab_rails['redis_port'] = 6379
 Finally run reconfigure, you might find it useful to run a check and
-a service status to make sure everything has been setup correctly.
+a service status to make sure everything has been set up correctly.
     sudo gitlab-ctl reconfigure  
     sudo gitlab-rake gitlab:check  

doc/university/support/README.md

@@ -37,7 +37,7 @@ Continue to look over remaining portions of the [University Overview](../README.
 Get your development machine ready to familiarize yourself with the codebase, the components, and to be prepared to reproduce issues that our users encounter
 - Install the [GDK](https://gitlab.com/gitlab-org/gitlab-development-kit)
-  - [Setup OpenLDAP as part of this](https://gitlab.com/gitlab-org/gitlab-development-kit#openldap)
+  - [Set up OpenLDAP as part of this](https://gitlab.com/gitlab-org/gitlab-development-kit#openldap)
 #### Become comfortable with the Installation processes that we support

doc/university/training/end-user/README.md

@@ -80,7 +80,7 @@ git config --global user.name "Your Name"
 git config --global user.email you@example.com
 ```    
-- If you don't use the global flag you can setup a different author for
+- If you don't use the global flag you can set up a different author for
   each project
 - Check settings with:

doc/update/4.2-to-5.0.md

@@ -32,7 +32,7 @@ cd /home/git/
 sudo -u git -H git clone https://github.com/gitlabhq/gitlab-shell.git /home/git/gitlab-shell
 ```
-## 3. setup gitlab-shell
+## 3. set up gitlab-shell
 ```bash
 # chmod all repos and files under git

doc/update/7.5-to-7.6.md

@@ -82,7 +82,7 @@ git diff origin/7-5-stable:config/gitlab.yml.example origin/7-6-stable:config/gi
 * HTTP setups: Make `/etc/nginx/sites-available/gitlab` the same as [`lib/support/nginx/gitlab`][nginx] but with your settings
 * HTTPS setups: Make `/etc/nginx/sites-available/gitlab-ssl` the same as [`lib/support/nginx/gitlab-ssl`][nginx-ssl] but with your setting
-#### Setup time zone (optional)
+#### Set up time zone (optional)
 Consider setting the time zone in `gitlab.yml` otherwise GitLab will default to UTC. If you set a time zone previously in [`application.rb`][app] (unlikely), unset it.

doc/update/7.6-to-7.7.md

@@ -82,7 +82,7 @@ git diff origin/7-6-stable:config/gitlab.yml.example origin/7-7-stable:config/gi
 * HTTP setups: Make `/etc/nginx/sites-available/gitlab` the same as [`lib/support/nginx/gitlab`][nginx] but with your settings
 * HTTPS setups: Make `/etc/nginx/sites-available/gitlab-ssl` the same as [`lib/support/nginx/gitlab-ssl`][nginx-ssl] but with your setting
-#### Setup time zone (optional)
+#### Set up time zone (optional)
 Consider setting the time zone in `gitlab.yml` otherwise GitLab will default to UTC. If you set a time zone previously in [`application.rb`][app] (unlikely), unset it.