Correct "setup" and "set up" grammar sitewide

README.md

@@ -66,7 +66,7 @@ properties.
 ## Production build
 Before building the static files, ensure you have a GitLab.com `PRIVATE_TOKEN`
-environment variable setup. This is required so that Middleman can automatically
+environment variable set up. This is required so that Middleman can automatically
 build the [direction page](https://about.gitlab.com/direction/).
 ```sh

data/case_studies/cncf.yml

@@ -87,7 +87,7 @@ customer_study_content:
       - |
         “The initial desire was to have a per repo environment configuration that
         didn't require setting up Jenkins, but could handle the complexity of managing
-        the cross-project configuration. It was a lot simpler to setup and use GitLab,”
+        the cross-project configuration. It was a lot simpler to set up and use GitLab,”
         said McClimans. “We needed something that was easy for people to get started
         and so they could collaborate together in a meaningful way.”

data/release_posts/2017_07_22_gitlab_9_4_released.yml

@@ -115,7 +115,7 @@ features:
       description: |
         Using both Trello and GitLab? Now you can make that experience even better with the new [GitLab Power-Up](https://docs.gitlab.com/ee/integration/trello_power_up.html)!
         In Trello, when viewing one of your boards, simply go to `Power-Ups` and scroll
-        to the `GitLab` Power-Up. After set-up, you will be able to attach merge requests
+        to the `GitLab` Power-Up. After setup, you will be able to attach merge requests
         to Trello cards.
         In Trello, you will need to configure your domain, such as `gitlab.com/api/v4` for GitLab.com,

data/release_radars.yml

@@ -11,7 +11,7 @@
   tagline: "Accelerate software delivery and see changes in real time with our Web IDE"
   description:
     - "Developing web applications is faster and easier when developers don’t have to set up a new project from scratch and can make changes in real time. In our latest release, the live preview in GitLab’s Web IDE allows users to iterate faster by seeing the outcome before committing the changes."
-    - "To speed up the installation process, the Cloud Native Helm Chart is now generally available to help you get started with GitLab on Kubernetes. And manifest files help you move forward faster by allow you to import larger project structures with multiple repositories all together, for instance enabling the import of repositories based on the <a href='https://source.android.com/' target='blank'>Android Open Source Project (AOSP)</a>. Custom project templates allow users to get started faster by eliminating tedious set-up tasks."
+    - "To speed up the installation process, the Cloud Native Helm Chart is now generally available to help you get started with GitLab on Kubernetes. And manifest files help you move forward faster by allow you to import larger project structures with multiple repositories all together, for instance enabling the import of repositories based on the <a href='https://source.android.com/' target='blank'>Android Open Source Project (AOSP)</a>. Custom project templates allow users to get started faster by eliminating tedious setup tasks."
     - "Join us for a live broadcast to learn more about GitLab’s latest enhancements including how to preview your live JavaScript web application in the Web IDE and see your changes in real time right next to the code."
   form: 1419
   what_we_cover:

source/cloud-images/index.html.md

@@ -36,7 +36,7 @@ will complete for the packaging team they will reinstate their ownership as main
     1. Create issue for first time image
     2. Gathering of documentation on integrating with the Cloud Partner
     3. Understand joint marketing efforts opportunities for collaboration on launch
-    4. Setup GitLab account on Cloud Partner’s system
+    4. Set up GitLab account on Cloud Partner’s system
     5. Optional: Initiate technical call with Omnibus team member and partner tech/product lead (at request of Omnibus team)
     6. Introduce Partner Marketing to marketing contacts from Cloud Partner

source/contributing/index.html.haml

@@ -43,7 +43,7 @@ extra_css:
           :markdown
             These instructions are for development of GitLab Community Edition specifically. Please note that use of the GitLab Development Kit is currently experimental on Windows. macOS or Linux are recommended for the best contribution experience.
-            1. Download and setup the [GitLab Development Kit](https://gitlab.com/gitlab-org/gitlab-development-kit), see the [GDK README](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/README.md) for instructions on setting it up and [Troubleshooting](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/howto/troubleshooting.md) if you get stuck.
+            1. Download and set up the [GitLab Development Kit](https://gitlab.com/gitlab-org/gitlab-development-kit), see the [GDK README](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/README.md) for instructions on setting it up and [Troubleshooting](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/howto/troubleshooting.md) if you get stuck.
             1. Fork the GitLab CE project.
             1. Choose an issue to work on.
               * You can find easy issues by [looking at issues labeled Accepting Merge Requests and sorting issues by weight](https://gitlab.com/gitlab-org/gitlab-ce/issues?assignee_id=0&label_name%5B%5D=Accepting%20Merge%20Requests&sort=weight_asc), low-weight issues will be the easiest to accomplish.

source/features/gitlab-ci-cd/index.html.haml

@@ -154,7 +154,7 @@ extra_css:
           %ul
             %li
               %b Quick project setup:
-              Add projects with a single click, all hooks are setup automatically via the GitLab API.
+              Add projects with a single click, all hooks are set up automatically via the GitLab API.
             %li
               %b Merge request integration:
               See the status of each build within the Merge Request in GitLab.

source/handbook/board-meetings/index.html.md

@@ -41,7 +41,7 @@ Agenda (the agenda should also include the zoom link at the top)
 Make sure to:
 Determine which participants will be attending remotely and in-person to ensure there is enough room.
-Test Zoom set-up at least 1 hour before and at most 2 days before
+Test Zoom setup at least 1 hour before and at most 2 days before
 Ensure remote participants feel invited and welcomed
 ## Quarterly Q&A with the Board

source/handbook/business-ops/index.html.md

@@ -510,7 +510,7 @@ Select and set up your presentation space. Pick a spot with good wifi, and we re
 ##### Before the Presentation
 Try to get a good sleep the night before, and, if the presentation is in the morning, wake up early enough to run through your notes at least once. Review our [Positioning FAQ](/handbook/positioning-faq/), or keep the page handy in case you are asked in the Q&A about how GitLab compares to our competitors.
-#### Logistical Set-Up
+#### Logistical Setup
 ##### Marketo & SFDC

source/handbook/developer-onboarding/index.html.md

@@ -81,7 +81,7 @@ Linux distributions and macOS. In order to maintain portability, we need to
 avoid adding extra dependencies and use of exotic database extensions. Every
 time you choose between changes in the application code or adding new
 dependencies, you should give priority to the first because this is easier to
-maintain and setup. If you still need to bring new dependencies to GitLab, ask
+maintain and set up. If you still need to bring new dependencies to GitLab, ask
 another developer or the CTO for advice.
 ### Submit your code

source/handbook/ea/index.html.md

@@ -89,7 +89,7 @@ There should be one invite for all attendees that includes the following:
 Make sure to:
-* Test Zoom set-up at least 1 hour before and at most 2 days before
+* Test Zoom setup at least 1 hour before and at most 2 days before
 * Ensure remote participants feel invited and welcomed
 ## Email

source/handbook/engineering/dev-backend/distribution/index.html.md

@@ -30,7 +30,7 @@ Distribution team vision is shown below, and not limited to:
 * GitLab runs on low resources systems such as Raspberry Pi.
 * All GitLab features are installed and configured by default.
 * GitLab is able to automatically upgrade itself.
-* Installation interface to setup and configure GitLab.
+* Installation interface to set up and configure GitLab.
 * Any GitLab installation is able to report installation/upgrade errors automatically.
 * Setting up GitLab in HA configuration is automated and simple.
 * All installation methods are automatically tested before release.

source/handbook/engineering/monitoring/index.html.md

@@ -45,7 +45,7 @@ We collect data using InfluxDB and Prometheus, leveraging available exporters li
 #### Adding Dashboards
-To learn how to setup a new graph or dashboard using Grafana, take a look at the following resources
+To learn how to set up a new graph or dashboard using Grafana, take a look at the following resources
 - [Guide to setting up Grafana dashboards by Grafana](http://docs.grafana.org/guides/getting_started/)
 - [YouTube video showing how to set up a dashboard](https://www.youtube.com/watch?v=sKNZMtoSHN4&index=7&list=PLDGkOdUX1Ujo3wHw9-z5Vo12YLqXRjzg2)

source/handbook/marketing/marketing-sales-development/content/index.html.md

@@ -357,7 +357,7 @@ You can find a list of evergreen content assets their primary channel for promot
 When you post a link on Facebook or Twitter, either you can see only a link, or a full interactive card, which displays information about that link: title, **description**, **image** and URL.
-For Facebook these cards are configured via [OpenGraph Meta Tags][OG]. Twitter Cards were recently setup for our website as well.
+For Facebook these cards are configured via [OpenGraph Meta Tags][OG]. Twitter Cards were recently set up for our website as well.
 Please compare the following images illustrating post's tweets.

source/handbook/marketing/marketing-sales-development/oldBDRHandbook.html.md

@@ -253,7 +253,7 @@ Three things in three minutes about the:
 ### Warm Discovery Calls
 Purpose: To qualify leads faster and more accurately (SQL Qualification Criteria) than in an email exchange.
-Process: In your reply message to setup/initiate a call, ask a few of your normal BDR questions to prep for the call. To save a step in emails include your Calendly link so leads may schedule the call directly.
+Process: In your reply message to set up/initiate a call, ask a few of your normal BDR questions to prep for the call. To save a step in emails include your Calendly link so leads may schedule the call directly.
     “Hi (lead name), this is (BDR) from GitLab. How are you today?”

source/handbook/marketing/marketing-sales-development/online-marketing/index.html.md

@@ -97,7 +97,7 @@ You can use the calendar in the top right to set the active date range. You can
 #### Annotations
-Annotations are used to mark a point in time in Google Analytics. They can be used to mark an important event such as a change to the set-up of Google Analytics, or an event that heavily impacted traffic positively or negatively.
+Annotations are used to mark a point in time in Google Analytics. They can be used to mark an important event such as a change to the setup of Google Analytics, or an event that heavily impacted traffic positively or negatively.
 To create an annotation, double-click on a date. The double-click will bring up the annotation field where you can enter details, and select `private` or `public`. Public annotations can be seen by anyone that has access to that view within Google Analytics, and private annotations can only be seen by you.

source/handbook/marketing/marketing-sales-development/sdr/index.html.md

@@ -434,7 +434,7 @@ Tips
 ### Warm Prospecting Call Example
 Purpose: To qualify leads faster and more accurately (Sales Acceptance Criteria) than in an email exchange.
-Process: In your reply message to setup/initiate a call, ask a few of your normal BDR questions to prep for the call. To save a step in emails include your Calendly link so leads may schedule the call directly.
+Process: In your reply message to set up/initiate a call, ask a few of your normal BDR questions to prep for the call. To save a step in emails include your Calendly link so leads may schedule the call directly.
     “Hi (lead name), this is (BDR) from GitLab. How are you today?”

source/handbook/marketing/product-marketing/demo/i2p/index.html.md

@@ -110,7 +110,7 @@ just to save myself some typing.
 > * Set `Project name` to `minimal-ruby-app`
 > * Make it public
-## Setup GitLab Auto DevOps
+## Set up GitLab Auto DevOps
 Now we’re ready to configure GitLab Auto DevOps, which is the easiest way to
 configure GitLab CI/CD with a bunch of best practices already built in. Let’s go

source/handbook/marketing/product-marketing/demo/index.html.md

@@ -19,7 +19,7 @@ There are 3 basic demos types:
 These demos come in different formats:
 * videos - good for everyone to self-demo by passively watching
 * click-throughs (screenshots on slides) - good for disconnected situations (like conferences) and for interactive self demos
-* live (instructions for how to setup and run demos live) - enables everyone (especially GitLab sales) to setup and run through the demo live on their own system resources. Allows for spontaneous deep diving - not always a good thing).
+* live (instructions for how to set up and run demos live) - enables everyone (especially GitLab sales) to set up and run through the demo live on their own system resources. Allows for spontaneous deep diving - not always a good thing).
 # Videos

source/handbook/sales/POC/index.html.md

@@ -156,7 +156,7 @@ Calls may be recorded with customer consent, and recordings may be stored in the
 #### Week one
-*  Work with customer to setup and configure GitLab if required
+*  Work with customer to set up and configure GitLab if required
 *  Intro to GitLab via demo covering areas specific to customer needs
 *  Conduct cadence calls as agreed in kickoff meeting