Correct "setup" and "set up" grammar sitewide

source/posts/2015-05-06-why-were-replacing-gitlab-ci-jobs-with-gitlab-ci-dot-yml.html.md

@@ -16,7 +16,7 @@ as it integrates deeply with GitLab.
 Up until now, to set up the build / deploy commands you had to
 go into GitLab CI and edit the scripts in a form. This made
-it very low-threshold to setup, but it felt lacking.
+it very low-threshold to set up, but it felt lacking.
 We're glad to tell you we'll get a better solution built on the principles and libraries of [Travis CI](https://www.travis-ci.org):
 `.gitlab-ci.yml`.
@@ -63,7 +63,7 @@ On top of that, a fork can easily add dependencies to its `.gitlab-ci.yml` file.
 At the moment you can't easily run different scripts for different branches.
 By moving the script to the repository this opens up a whole new world of
-specific builds for certain branches. For instance, you could setup your
+specific builds for certain branches. For instance, you could set up your
 time-intense integration tests to only run on pushes to your `production` branch
 - and on success, deploy your code immediately.

source/posts/2015-06-22-gitlab-7-12-released.html.md

@@ -29,7 +29,7 @@ With Alexandre's contribution, GitLab can now be configured to act as
 a SAML 2.0 Service Provider. This allows GitLab to consume assertions from a SAML 2.0
 Identity Provider (IdP) such as Microsoft Active Directory Federation Services to authenticate users.
-See our [documentation on how to setup SAML integration](http://doc.gitlab.com/ce/integration/saml.html).
+See our [documentation on how to set up SAML integration](http://doc.gitlab.com/ce/integration/saml.html).
 ## Web Hook for Comments

source/posts/2015-08-19-quayio.html.md

@@ -17,7 +17,7 @@ By bringing Quay.io together with GitLab, users are able to develop easier and f
 <!-- more -->
-## How to setup a GitLab project with a Dockerfile
+## How to set up a GitLab project with a Dockerfile
 Getting started with GitLab and Quay.io can be done in a few simple steps.
@@ -81,7 +81,7 @@ Choose a GitLab repository to build (or enter the repository in the repository b
 You will be asked for other information pertaining to the build, such as the subdirectory that contains the Dockerfile (usually this is just “/”), what branches/tags to build (by default: everything) and whether to use a [Robot Account](http://docs.quay.io/glossary/robot-accounts.html) as pull credentials (only required if you have a private base image on Quay.io).
-Once this information is entered, the build trigger will be setup on GitLab:
+Once this information is entered, the build trigger will be set up on GitLab:
 ![Final Quay.io trigger dialog](/images/quayio/dialog2.png)

source/posts/2015-12-14-getting-started-with-gitlab-and-gitlab-ci.html.md

@@ -50,7 +50,7 @@ What started as a side project [three years ago][ci-first-post], has now
 become one of GitLab's key features. Back then, it was a separate application
 that talked to GitLab via webhooks. Now, starting from GitLab 8.0,
 GitLab CI has been [fully integrated with GitLab itself][8-post]. No more need
-to setup and maintain another application, which means less work for you or
+to set up and maintain another application, which means less work for you or
 your Ops team.
 GitLab CI is enabled by default on new projects, so you can start using its

source/posts/2016-02-18-gitlab-dot-com-now-supports-an-alternate-git-plus-ssh-port.html.md

@@ -62,7 +62,7 @@ it runs GitLab itself, and that's assuming you are running GitLab with HTTPS
 use a separate host which forwards port 443 to port 22 of your GitLab instance.
 You can do this with HAProxy or any other loadbalancer, or even with IPTables.
-In GitLab.com's case, we have setup a separate Azure availability set with two
+In GitLab.com's case, we have set up a separate Azure availability set with two
 HAProxy nodes exactly the same configured as for GitLab.com. The only thing
 that differs is the creation of a different Azure loadbalancer in that
 availability set which forwards TCP connections from port 443 to port 22.

source/posts/2016-02-22-gitlab-8-5-released.html.md

@@ -153,7 +153,7 @@ set them up.
 For GitLab.com users: Pages with CNAME and TLS support are fully live and
 ready to use!
-> [Learn how to setup your own page in our Gitlab Pages user documentation](http://doc.gitlab.com/ee/pages/README.html)
+> [Learn how to set up your own page in our Gitlab Pages user documentation](http://doc.gitlab.com/ee/pages/README.html)
 > [GitLab Pages administration documentation](http://doc.gitlab.com/ee/pages/administration.html)

source/posts/2016-03-01-gitlab-runner-with-docker.html.md.erb

@@ -19,9 +19,9 @@ optimal pipeline for their needs.
 This tutorial will demonstrate how to get started with a CI workflow using
 [GitLab Runner](https://gitlab.com/gitlab-org/gitlab-runner).
-We will first setup a sample NodeJS project hosted on Gitlab.com to run tests
+We will first set up a sample NodeJS project hosted on Gitlab.com to run tests
 on build machines provided by GitLab Inc.
-Then, we will setup and configure our own specific runner on a private server.
+Then, we will set up and configure our own specific runner on a private server.
 Finally we will go over some good practices to speed up the build time as the project grows.
 By the end of this tutorial you will feel comfortable building your own
 CI solution, custom-tailored for your existing projects.

source/posts/2016-03-14-gitlab-in-case-you-missed-it.html.md

@@ -75,7 +75,7 @@ Since the pool is shared across all projects on GitLab.com, sometimes it can
 take a while to wait for your project's build to be processed.
 If you are not satisfied with the Shared runners performance, you can
-[setup a runner](/2016/03/01/gitlab-runner-with-docker/)
+[set up a runner](/2016/03/01/gitlab-runner-with-docker/)
 on your own server and connect it to one or more projects.
 Don't forget that you can install GitLab on your own server as well. 

source/posts/2016-04-19-gitlab-partners-with-digitalocean-to-make-continuous-integration-faster-safer-and-more-affordable.html.md

@@ -87,4 +87,4 @@ a $250 credit* to use to host your own Runners on DigitalOcean.
 ## Need help setting up your Runners?
 For help setting up your GitLab Runners, read the tutorial documentation,
-[How to setup GitLab Runner on DigitalOcean](/2016/04/19/how-to-set-up-gitlab-runner-on-digitalocean/).
+[How to set up GitLab Runner on DigitalOcean](/2016/04/19/how-to-set-up-gitlab-runner-on-digitalocean/).

source/posts/2016-05-05-getting-started-gitlab-and-shippable.html.md

@@ -27,7 +27,7 @@ their repositories in GitLab to production."
 Our new Shippable integration for GitLab supports running builds for your push commits, merge requests 
 and even show the build status in GitLab, so you can enjoy the power of Shippable within GitLab. To know 
-more about how to setup Shippable CI with GitLab, read on.
+more about how to set up Shippable CI with GitLab, read on.
 ---

source/posts/2016-06-10-ssg-overview-gitlab-pages-part-2.html.md

@@ -124,7 +124,7 @@ The majority of SSGs use **markdown engines** for this purpose. But there are ma
 lightweight markup languages used likely, such as [AsciiDoc], [Textile] and [ReStructuredText].
 Among those SSGs which use markdown markup, generally we are allowed to choose which markdown engine
-we want to use. It is setup on the site configuration.
+we want to use. It is set up on the site configuration.
 For example, in Ruby there are a handful of Markdown implementations:
 [Kramdown], [RDiscount], [Redcarpet], [RedCloth].
@@ -366,7 +366,7 @@ Follow [@GitLab][twitter] on Twitter and stay tuned for updates!
 ### Useful links
 - [GitLab Pages Quick Start][pages] - learn how to get started with GitLab Pages by forking an existing project
-- [GitLab Pages on GitLab.com][post-pages] - learn how to setup a GitLab Pages project from strach
+- [GitLab Pages on GitLab.com][post-pages] - learn how to set up a GitLab Pages project from strach
 - [GitLab Pages Docs][pages-ee] - the official documentation with all the details you might be interested in
 - [SSGs Part 1: Static vs Dynamic Websites][part-1] - the first post of this series
 - [SSGs Part 3: Build any SSG site with GitLab Pages][part-3] - the third post of this series

source/posts/2016-06-17-ssg-overview-gitlab-pages-part-3-examples-ci.html.md

@@ -9,7 +9,7 @@ author_twitter: virtuacreative
 image_title: '/images/blogimages/ssg-gitlab-pages-series/ssg-overview-gitlab-pages-part-3-cover.jpg'
 ---
-Which **Static Site Generators** (SSGs) can I use with **GitLab Pages**? How to setup GitLab CI to build
+Which **Static Site Generators** (SSGs) can I use with **GitLab Pages**? How to set up GitLab CI to build
 my SSG site? Where can I find some examples?
 If these questions ring a bell, this **series of posts** is for you! We prepared three articles around

source/posts/2016-06-28-get-started-with-openshift-origin-3-and-gitlab.html.md

@@ -92,7 +92,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

source/posts/2016-07-13-how-to-setup-a-gitlab-instance-on-microsoft-azure.html.md

 ---
-title: "How to Setup a GitLab Instance on Microsoft Azure"
+title: "How to Set Up a GitLab Instance on Microsoft Azure"
 author: Dave Wentzel
 author_twitter:
 categories: engineering

source/posts/2016-07-22-gitlab-8-10-released.html.md

@@ -225,7 +225,7 @@ Slack channel GitLab should report.
 ![Improved Slack integration with GitLab 8.10](/images/8_10/slack.png)
-> [Read how to setup the Slack service in GitLab](http://docs.gitlab.com/ee/project_services/slack.html)
+> [Read how to set up the Slack service in GitLab](http://docs.gitlab.com/ee/project_services/slack.html)
 ## Updated Emoji!

source/posts/2016-08-26-ci-deployment-and-environments.html.md.erb

@@ -57,7 +57,7 @@ Let’s try to automate it using GitLab CI.
 ## First Automated Deployment
 With GitLab, there's no difference on what commands to run.
-You can setup GitLab CI according to your needs as if it was your local terminal on your computer. As long as you execute commands there, you can tell
+You can set up GitLab CI according to your needs as if it was your local terminal on your computer. As long as you execute commands there, you can tell
 CI to do the same for you in GitLab.
 Put your script to `.gitlab-ci.yml` and push your code - that’s it: CI triggers
 a _job_ and your commands are executed.

source/posts/2016-10-25-gitlab-workflow-an-overview.html.md.erb

@@ -81,7 +81,7 @@ Whenever you want to keep the discussion presented in a issue within your team o
 ### Due dates
-Every issue enables you to attribute a [due date][due-dates-post] to it. Some teams work on tight schedules, and it's important to have a way to setup a deadline for implementations and for solving problems. This can be facilitated by the due dates.
+Every issue enables you to attribute a [due date][due-dates-post] to it. Some teams work on tight schedules, and it's important to have a way to set up a deadline for implementations and for solving problems. This can be facilitated by the due dates.
 When you have due dates for multi-task projects—for example, a new release, product launch, or for tracking tasks by quarter—you can use [milestones](#milestones).
@@ -372,7 +372,7 @@ GitLab Workflow helps your team to get faster from idea to production using a si
 - <i class="fas fa-check-circle-o fa-fw" style="color: green;"></i> It's **effective**, because you get your desired results.
 - <i class="fas fa-check-circle-o fa-fw" style="color: green;"></i> It's **efficient**, because you achieve maximum productivity with minimum effort and expense.
 - <i class="fas fa-check-circle-o fa-fw" style="color: green;"></i> It's **productive**, because you are able to plan effectively and act efficiently.
-- <i class="fas fa-check-circle-o fa-fw" style="color: green;"></i> It's **easy**, because you don't need to setup different tools to accomplish what you need with just one, GitLab.
+- <i class="fas fa-check-circle-o fa-fw" style="color: green;"></i> It's **easy**, because you don't need to set up different tools to accomplish what you need with just one, GitLab.
 - <i class="fas fa-check-circle-o fa-fw" style="color: green;"></i> It's **fast**, because you don't need to jump across multiple platforms to get your job done.
 A new GitLab version is released every single month (on the 22nd), for making it a better integrated solution for software development, and for bringing teams to work together in one single and unique interface.

source/posts/2016-11-03-working-at-gitlab-30-days-later.html.md

@@ -13,7 +13,7 @@ Much like [Emily von Hoffmann](https://twitter.com/emvonhoffmann), I too recentl
 ## The Wow Factor
-One of the most impressive part of the GitLab culture is it's efficiency. Although it is listed as a value, I did not expect it to be so pronuounced. Monthly releases for GitLab CE and EE is just the tip of the iceberg of how much this team can accomplish in a short amount of time. I was amazed at how everything was ready for me before my first day of work. My GitLab email, my slack account, my swag codes and many onboarding items were all setup a few days after I signed my offer letter. I even had my business cards before I started my first day and got to hand them out to my coworkers before I left my previous company!
+One of the most impressive part of the GitLab culture is it's efficiency. Although it is listed as a value, I did not expect it to be so pronuounced. Monthly releases for GitLab CE and EE is just the tip of the iceberg of how much this team can accomplish in a short amount of time. I was amazed at how everything was ready for me before my first day of work. My GitLab email, my slack account, my swag codes and many onboarding items were all set up a few days after I signed my offer letter. I even had my business cards before I started my first day and got to hand them out to my coworkers before I left my previous company!
 The efficiency of the team paired with the fact that everyone is so talented at what they do, truly creates an incredibly productive environment. I cannot agree more with [general guideline #1](/handbook/general-guidelines):

source/posts/2016-11-22-gitlab-8-14-released.html.md

@@ -228,7 +228,7 @@ Related MR: <https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7413>
 ### A more silent GitLab in JIRA
-When you setup the JIRA service within GitLab, by default, every commit and
+When you set up the JIRA service within GitLab, by default, every commit and
 merge request in GitLab that referenced a JIRA issue created a comment in this
 issue in JIRA. Some people like having the complete details of what's going on,
 others prefer this to be more silent.

source/posts/2016-12-01-how-to-keep-your-fork-up-to-date-with-its-origin.html.md

@@ -45,7 +45,7 @@ Under your forked project's **Settings**, navigate to **Mirror Repository**:
 ![fork - enable automatic repository update](/images/blogimages/how-to-keep-your-fork-up-to-date-with-its-origin/setup-automatic-mirror.png){:.shadow}
 <i class="far fa-arrow-alt-circle-right gitlab-purple" aria-hidden="true"></i>
-**Third**. Setup the **mirror user**: it's the user whose new commits to the upstream project will be attributed to in your fork.
+**Third**. Set up the **mirror user**: it's the user whose new commits to the upstream project will be attributed to in your fork.
 <i class="fas fa-check-circle-o" aria-hidden="true" style="color: green"></i>
 **Done**! Once an hour, GitLab will pull the upstream for you, and keep your fork up-to-date!