Fix typos in www-gitlab-com entire project

source/company/okrs/2018-q2/index.html.md

@@ -414,7 +414,7 @@ title: "Calendar Year 2018 Q2 OKRs"
 ### Services Support
 * GOOD
-  * With better staffing we've been able to consistenly increase our SLA performance and work through a sizeable backlog.
+  * With better staffing we've been able to consistently increase our SLA performance and work through a sizeable backlog.
   * Services Agents have done an great job collaborating on process and documentation.
 * BAD
   * This quarters hires are starting later in the quarter than we would have liked.

source/company/okrs/2018-q3/index.html.md

@@ -529,7 +529,7 @@ title: "Calendar Year 2018 Q3 OKRs"
   * Establishing a more streamlined candidate to hire process.
   * Clarify expectations for each level of Support Engineering and Support Agent job roles to complement career growth.
   * Ramp up sourcing/hiring in APAC
-  * Partner with sales to take especially great care of important customers/propsects prior to renewels and new contracts
+  * Partner with sales to take especially great care of important customers/prospects prior to renewels and new contracts
 ### Support - Self-Managed
@@ -553,7 +553,7 @@ title: "Calendar Year 2018 Q3 OKRs"
   * Hit stride in hiring: additional headcount matches volume well.
   * Worked cross-team with Security, Accounts and SMB Team on improving process
 * Bad
-  * Ticket volume for .com customers is at a level that a miss severly affects SLA performance
+  * Ticket volume for .com customers is at a level that a miss severely affects SLA performance
   * GitHost app stopped upgrading customer instances after a bad version was posted on version.gitlab.com
 * Try
   * Revisiting breach notifications to ensure we aren't missing tickets because of visibility

source/company/okrs/2018-q4/index.html.md

@@ -43,7 +43,7 @@ title: "Calendar Year 2018 Q4 OKRs"
   * Director of Business Operations: Top of funnel process and metrics defined and aligned with bottom of funnel. *70%*
     * Data & Analytics: Able to define and calculate Customer Count, MRR and ARR by Customer, Churn by Cohort, Reason for Churn *75%* - Some metrics still require [review](https://about.gitlab.com/handbook/business-ops/data-quality-process/)
   * Director of Business Operations: Looker Explores generated for Customer Support, PeopleOps, GitLab.com Event Data, Marketing Data *100%*
-    * Data & Analytics: Single Data Lake for all raw and transformed company data - migration to Snowflake compelte with DevOps workflow in place, GitLab.com production data extracted and modelled *75%*
+    * Data & Analytics: Single Data Lake for all raw and transformed company data - migration to Snowflake complete with DevOps workflow in place, GitLab.com production data extracted and modelled *75%*
     * Data & Analytics: Configuration and Business processes documented with integrity tests that sync back with upstream source (SFDC), dbt docs deployed *100%*
 * Product: Listen to and prioritize top feature requests from customers through sales / customer success. 10 features prioritized. => **130% Complete** [13 items prioritized](https://docs.google.com/document/d/1dAs9HoAbuiRzYYvk-AFMggbN-1Hb1l6L17jMzLePbkA/edit#heading=h.qnnbz6f7mo5y)
@@ -103,7 +103,7 @@ title: "Calendar Year 2018 Q4 OKRs"
       * Merge smaller changes more frequently: > 6 average MRs merged per week : 79% achieved - [Actual weekly average](https://quality-dashboard.gitlap.com/groups/gitlab-org/teams/monitoring) 4.75 MRs
     * [Kamil](https://about.gitlab.com/company/team/#ayufanpl):
       * Improve scalability: Reduce CI database footprint as part of [Ensure CI/CD can scale in future](https://gitlab.com/gitlab-org/gitlab-ce/issues/46499) with [Use BuildMetadata to store build configuration in JSONB form](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21499): Done (100%)
-      * Continuous Deployment: Help with building CD features needed to continously deploy GitLab.com by closing 5 [issues related to Object Storage](https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name=Object%20Storage) that are either ~"technical debt" or ~"bug": 2 out of 5 (40%)
+      * Continuous Deployment: Help with building CD features needed to continuously deploy GitLab.com by closing 5 [issues related to Object Storage](https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name=Object%20Storage) that are either ~"technical debt" or ~"bug": 2 out of 5 (40%)
     * CI/CD:
       * Spend no more than 15 point of our [error budget]: 30/15 [#5375](https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/5375), [#564](https://gitlab.com/gitlab-com/gl-infra/production/issues/564) (0% - Spent double our goal)
       * Merge smaller changes more frequently: >10 average MRs merged per week. (100% - Actual weekly average was 19 MRs)
@@ -396,7 +396,7 @@ title: "Calendar Year 2018 Q4 OKRs"
 * BAD
   * 1 team member left
   * 3 out of 5 people without significant pre-existing Golang experience did not end up contributing to Golang projects
-  * We continue to overestimate the amount of work we can get done in a month, through underestimating the size of individual issues, resulting in higher pressure around the feature freeze and more slipping to the next release than desireable
+  * We continue to overestimate the amount of work we can get done in a month, through underestimating the size of individual issues, resulting in higher pressure around the feature freeze and more slipping to the next release than desirable
   * Security issues have taken up a significant portion of each of the last few releases, resulting in less time to work on direction features
 * TRY
   * Continue to have people without Golang experience work on issues that require them to get familiar with our Golang components (Gitaly, Workhorse)
@@ -581,7 +581,7 @@ title: "Calendar Year 2018 Q4 OKRs"
   * Hired two test automation engineers.
   * Completed Patroni Replication Manager testing with GitLab QA.
   * Completed TLS Depreciation testing with GitLab QA.
-  * Completed Rails 5 migration testing wtih GitLab QA.
+  * Completed Rails 5 migration testing with GitLab QA.
 * BAD
   * An update to the clone / fork button cause GitLab QA tests to break for 4 days.
   * Review Apps are broken (no DNS record) due to an increasing number of DNS records and too many API calls to AWS.
@@ -662,7 +662,7 @@ title: "Calendar Year 2018 Q4 OKRs"
 #### EMEA
 * GOOD
-  * Hired 2 Suport Agents per target
+  * Hired 2 Support Agents per target
   * Focused learning objectives for team with quarterly learning goals
   * Groundwork for knwledge sharing, documentation updates, search and tracking
   * Streamline Zendesk configuration to improve agent efficienc

source/company/okrs/fy20-q2/index.html.md

@@ -24,7 +24,7 @@ This fiscal quarter will run from May 1, 2019 to July 31, 2019.
     1.  Digital Marketing Programs: Drive traffic to docs and from docs to about.gitlab.com via on-page optimization, improved cookie-ing, and remarketing, increase new user traffic to docs by 10% QoQ.
     1.  Field Marketing: Implement ABM Strategy. Baseline ABM metrics (# of contacts in named accounts, # of engaged contacts in named accounts), execute 1 ABM-style integrated campaign.
 1. CMO: Attract net-new developers and DevOps practitioners.  Deploy paid digital campaign focused on technical audience, enable retargeting of deeper technical content to docs visitors, launch GitLab "heroes" program, sign-up 1,500 users to 3 user conferences (500 each).
-    1.  PMM: Attract net-new develoeprs. Define and deliver a series of 5 webinars talks focused on DevOps practitioners, attract 1000 registrants to the 5 webinars (total).
+    1.  PMM: Attract net-new developers. Define and deliver a series of 5 webinars talks focused on DevOps practitioners, attract 1000 registrants to the 5 webinars (total).
     1.  Digital Marketing programs: Build out developer marketing paid digital program to target and attract developers and and to increase form fills for  the demo and increase .com users by 10% QoQ
     1.  Corp Marketing: Prominent presence at strategic industry events (KubeCon EU, DOES EMEA, OSCON). Capture over 15% of an engaged audience (through talks, social, booth scans, giveaways, dinners and meetings), Reach 10,000 people through technical evangelism efforts (such as talks, onboarding CNCF projects on GitLab CI), create 5 technical blog posts and social technical content from show content within 2 weeks of event.
     1.  Events: Announce user conferences. Drive 600 sign ups to the 2 events, align GitLab “heros” program with the user conferences, recruit 5 well-known speakers to be part of the event to drive sign ups.

source/company/team/structure/working-groups/data-poc/index.html.md

@@ -20,7 +20,7 @@ title: "Data POC Working Group"
 ## Business Goal
-To successfully excecute a proof of concept on a particular data analytics solution.
+To successfully execute a proof of concept on a particular data analytics solution.
 ## Exit Criteria

source/concurrent-devops/index.html.haml

@@ -64,5 +64,5 @@ extra_css:
       %p We believe everyone should be able to easily and efficiently contribute and set out to make this easy for teams of all types and sizes by creating a single, shared space where everyone can work concurrently, get all the information needed in one place, and see changes in real time.
   %section.tile.contribute-tile.flex-container.justify-center.align-center
     %img{ src: "/images/devops-tools/gitlab-logo.svg", alt: "Gitlab logo svg" }
-    %p GitLab accelerates your software development and delivery accross every stage of the DevOps lifecycle.
+    %p GitLab accelerates your software development and delivery across every stage of the DevOps lifecycle.
     %a.text-center{href: "/product/"} Learn more →

source/devops-tools/azure_devops/index.html.md

@@ -165,7 +165,7 @@ title: "Azure DevOps"
 ## Summary
 On September 10, 2018 Microsoft renamed VSTS to Azure DevOps and by Q1 2019 will rename TFS to Azure DevOps Server, and upgrade both with the same new user interface.
-Azure DevOps (VSTS) is a hosted cloud offering, and Azure DevOps Server (TFS), is an on-premises version. Both offer functionality that cover multiple stages of the DevOps lifecycle including planning tools, source code managment (SCM), and CI/CD. However, first development focus will be to Azure DevOps (SaaS). Their project manager shared that they are releasing on a 3-4 week pace. This seems evident based on their [published roadmap](https://docs.microsoft.com/en-us/azure/devops/release-notes/). The same project manager also shared that Azure DevOps Server (TFS) will be 3-4 months behind on adopting new features (also evident by their published roadmap). They are both from the same code base.
+Azure DevOps (VSTS) is a hosted cloud offering, and Azure DevOps Server (TFS), is an on-premises version. Both offer functionality that cover multiple stages of the DevOps lifecycle including planning tools, source code management (SCM), and CI/CD. However, first development focus will be to Azure DevOps (SaaS). Their project manager shared that they are releasing on a 3-4 week pace. This seems evident based on their [published roadmap](https://docs.microsoft.com/en-us/azure/devops/release-notes/). The same project manager also shared that Azure DevOps Server (TFS) will be 3-4 months behind on adopting new features (also evident by their published roadmap). They are both from the same code base.
 As part of their SCM functionality, both platforms offer two methods of version control.
@@ -178,7 +178,7 @@ Microsoft recommends customers use Git for version control unless there is a spe
 This is noteworthy given that in June of 2018 Microsoft purchased [GitHub](../github/), the Internets largest online code repository. This deal closed Oct 26th, 2018.
 ## Breakdown
-Because the Azure DevOps suite is so wide, similar to GitLab, a breakdown can be helpfull in understanding what we're dealing with. Go to this [breakdown page](https://about.gitlab.com/devops-tools/azure_devops/breakdown.html) for more details.
+Because the Azure DevOps suite is so wide, similar to GitLab, a breakdown can be helpful in understanding what we're dealing with. Go to this [breakdown page](https://about.gitlab.com/devops-tools/azure_devops/breakdown.html) for more details.
 ## Strengths
 * Microsoft can use its huge customer base to gain access to sell Azure DevOps. And not just it's current VSTS and TFS customers, but any of its customers buying enterprise software.

source/devops-tools/bitbucket/index.html.md

@@ -41,7 +41,7 @@ Atlassian Bitbucket gives teams Git code management, but also one place to plan
 Bitbucket supports  Mercurial or Git, but not SVN. GitLab does not support Mercurial or SVN.
-GitLab is a single application for the complete DevOps lifecycle with built-in project management, source code managemetn, CI/CD, monitoring and more. Bitbucket only does source code managment. You would need to use Atlassian Jira to get project managment, and Bamboo for CI/CD and Atlassian does not provide a monitoring solution. Addditionally, GitLab Ultimate comes with robust built-in security capabilities such as SAST, DAST, Container Scanning, Dependency Scanning, and more. Bitbucket does not support these capabilities, and Atlassian does not have a product for them.
+GitLab is a single application for the complete DevOps lifecycle with built-in project management, source code managemetn, CI/CD, monitoring and more. Bitbucket only does source code management. You would need to use Atlassian Jira to get project management, and Bamboo for CI/CD and Atlassian does not provide a monitoring solution. Addditionally, GitLab Ultimate comes with robust built-in security capabilities such as SAST, DAST, Container Scanning, Dependency Scanning, and more. Bitbucket does not support these capabilities, and Atlassian does not have a product for them.
 GitLab also offers a "prem" self-managed and "cloud" SaaS solution. GitLab runs the same exact code on it's SaaS platform that it offers to it's customers. This means customers can migrated from self-hosted to SaaS and back relatively easily and each solution maintains feature parity.

source/devops-tools/jira/index.html.md

@@ -38,9 +38,9 @@ title: "Jira Software"
 ## Summary
 Jira Software is an issue tracker and agile project management application.
-Portfolio for Jira Portfolio is a separate add-on that enables portoflio management in Jira Software.
+Portfolio for Jira Portfolio is a separate add-on that enables portfolio management in Jira Software.
 Jira Service Desk is a separate application to enable IT and customer service capablilities.
-Jira Core is a scaled down version of Jira Software that contains the general project managment capabilities without the software and agile-specific functionality of Jira Software.
+Jira Core is a scaled down version of Jira Software that contains the general project management capabilities without the software and agile-specific functionality of Jira Software.
 Jira is available via 3 deploment models:
@@ -62,13 +62,13 @@ Jira is available via 3 deploment models:
 ## Resources
 * [Jira Software](https://www.atlassian.com/software/jira)  
-* [Jira Portoflio](https://www.atlassian.com/software/jira/portfolio)  
+* [Jira Portfolio](https://www.atlassian.com/software/jira/portfolio)  
 * [Jira Service Desk](https://www.atlassian.com/software/jira/service-desk)  
 * [Jira Core](https://www.atlassian.com/software/jira/core)  
 ## Integrations
-GitLab has [Jira integration](https://about.gitlab.com/features/jira/) that allows Jira Software to be used as an issue tracker for the planning stage while using GitLab for the rest of the DevOps lifecycle: source code managment, CI/CD, and monitoring.
+GitLab has [Jira integration](https://about.gitlab.com/features/jira/) that allows Jira Software to be used as an issue tracker for the planning stage while using GitLab for the rest of the DevOps lifecycle: source code management, CI/CD, and monitoring.
 ## Pricing
 [Jira Software pricing](https://www.atlassian.com/software/jira/pricing)

source/direction/fulfillment/index.html.md

@@ -15,7 +15,7 @@ This is the product vision for Fulfillment. Fulfillment manages a variety of cat
 | Category | Description |
 | ------ |  ------ |
-| [Licensing](/direction/fulfillment/licensing) | How we fullfill our users purchases of GitLab Plans through license key distribution. |
+| [Licensing](/direction/fulfillment/licensing) | How we fulfill our users purchases of GitLab Plans through license key distribution. |
 | [Transactions](/direction/fulfillment/transactions) | How our users purchase GitLab Plans and add-ons, and how they manage their account information. |
 | [Telemetry](/direction/fulfillment/telemetry) | Insights into how users use our product. |

source/direction/fulfillment/licensing/index.html.md

@@ -40,7 +40,7 @@ viable, complete and lovable maturity levels.-->
 ### Sidney (Systems Administrator) - [Persona Description](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator)
-* 🙂 **Minimal** - Sidney can recieve a license key in some form and is able to apply it to their GitLab instance.
+* 🙂 **Minimal** - Sidney can receive a license key in some form and is able to apply it to their GitLab instance.
 * 😊 **Viable** - Sidney is able to manage their GitLab license keys in a centralised location and easily apply them to their organisation's GitLab instances. 
 * 😁 **Complete** - Sidney is able to perform all the things in the viable solution, and additionally is able to view license key metadata (e.g. which instance a license key is currently applied to, expiration dates, and min/max seats).
 * 😍 **Lovable** - Sidney doesn't need to do anything to manage their GitLab license keys. License keys are synchronized automatically from GitLab's license key server and are always up to date.

source/direction/fulfillment/transactions/index.html.md

@@ -19,7 +19,7 @@ and user journeys into this section. -->
 * [Documentation](https://docs.gitlab.com/ee/getting-started/subscription.html)
 * [All Epics](https://gitlab.com/groups/gitlab-org/-/epics?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=transactions)
-The Transactions category covers the [Customers application](https://gitlab.com/gitlab-org/customers-gitlab-com/), more commonly referred to as the Customer Portal or the Subscription Portal. This was created to serve as a billing engine for both self-managed and GitLab.com users. This is a separate application to GitLab, and requires a separate login to GitLab.com. Typically, users use the Transactions portal to purchase and manage their GitLab Plan subscriptions and GitLab add-ons, although some customers may handle their transactions through the GitLab Sales team or a Reseller. All of these user journies, both users of GitLab and GitLab team members, are the responsibility of Fulfillment.
+The Transactions category covers the [Customers application](https://gitlab.com/gitlab-org/customers-gitlab-com/), more commonly referred to as the Customer Portal or the Subscription Portal. This was created to serve as a billing engine for both self-managed and GitLab.com users. This is a separate application to GitLab, and requires a separate login to GitLab.com. Typically, users use the Transactions portal to purchase and manage their GitLab Plan subscriptions and GitLab add-ons, although some customers may handle their transactions through the GitLab Sales team or a Reseller. All of these user journeys, both users of GitLab and GitLab team members, are the responsibility of Fulfillment.
 Please reach out to  Luca Williams, Product Manager for Fulfillment ([E-Mail](luca@gitlab.com)/
 [Twitter](https://twitter.com/tipyn2903)) if you'd like to provide feedback or ask

source/direction/monitor/template.html.md.erb

@@ -43,7 +43,7 @@ experience, as well as emergent capabilities.
 We want to help teams resolve outages faster, accelerating both the
 troubleshooting and resolution of incidents. GitLab's single platform can
 analyze the incoming observability data with known CI/CD events and source code
-infomation, to automatically suggest potential root causes. GitLab's Web IDE can
+information, to automatically suggest potential root causes. GitLab's Web IDE can
 also provide an optimized coding experience, presenting the source code enriched
 with related observability data like stack traces.
@@ -51,7 +51,7 @@ with related observability data like stack traces.
    <iframe width="560" height="315" src="https://www.youtube.com/embed/ZgFqyXCsqPY?start=4120" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
 </figure>
-* Detect errors that are occuring via [Tracing](https://gitlab.com/groups/gitlab-org/-/epics/89),
+* Detect errors that are occurring via [Tracing](https://gitlab.com/groups/gitlab-org/-/epics/89),
   [Error Tracking](https://gitlab.com/groups/gitlab-org/-/epics/169) and [Metrics](https://gitlab.com/groups/gitlab-org/-/epics/190)
 * First class [Incidents](https://gitlab.com/groups/gitlab-org/-/epics/349),
   providing a single source of truth across the whole lifecycle for improved

source/direction/package/maven_repository/index.html.md

@@ -36,7 +36,7 @@ Key deliverables to achieve this are:
 - [JFrog Artifactory](https://www.jfrog.com/confluence/display/RTF/Maven+Repository)
 - [Sonatype Nexus](https://www.sonatype.com/nexus-repository-sonatype)
-- [GitHub](https://help.github.com/en/articles/configuring-maven-for-use-with-github-package-registry) has a product in beta, which allows you to authenticate, publish and delete packages. In addition, they support webhooks for receiving registry events when a package is published or udpated. 
+- [GitHub](https://help.github.com/en/articles/configuring-maven-for-use-with-github-package-registry) has a product in beta, which allows you to authenticate, publish and delete packages. In addition, they support webhooks for receiving registry events when a package is published or updated. 
 Historically, we've provided access to the GitLab Container Registry for free, but limited access to additional integrations, such as Maven, to our paid tier. However, with [GitHub's annoucement](https://github.blog/2019-05-10-introducing-github-package-registry/) to support a package registry for free, we are reevaluating this strategy. 

source/direction/plan/template.html.md.erb

@@ -88,7 +88,7 @@ in the given year):
 | Report | 2019 | 2020 | 2021 |
 | --- | --- | --- | --- |
 | [Gartner Enterprise Agile Planning Tools](https://www.gartner.com/doc/3872863/magic-quadrant-enterprise-agile-planning) | Visionaries | Leaders | Leaders, above all other providers |
-| [Forrester Value Stream Management Tools](https://www.forrester.com/report/The+Forrester+New+Wave+Value+Stream+Management+Tools+Q3+2018/-/E-RES141538) | Strong Perfomers | Leaders | Leaders, above all other providers |
+| [Forrester Value Stream Management Tools](https://www.forrester.com/report/The+Forrester+New+Wave+Value+Stream+Management+Tools+Q3+2018/-/E-RES141538) | Strong Performers | Leaders | Leaders, above all other providers |
 Our overaching goal is specific to successful companies of the future. This is a
 goal aligned with the [vision of GitLab](https://about.gitlab.com/direction/#vision),

source/direction/release/continuous_delivery/index.html.md

@@ -170,7 +170,7 @@ implemented via [gitlab-ce#20481](https://gitlab.com/gitlab-org/gitlab-ce/issues
 Our most popular customer request is [gitlab-ce#20481](https://gitlab.com/gitlab-org/gitlab-ce/issues/20481),
 which limits per-environment pipeline concurrency. This is an important
 feature because it allows teams to constrain concurrent deployments, making
-things more predictible and/or managing finite resources associated with
+things more predictable and/or managing finite resources associated with
 environments (for example, a single deploy and test cycle at a time to a
 performance testing environment.)

source/direction/release/feature_flags/index.html.md

@@ -64,7 +64,7 @@ was first being conceived [here](https://docs.google.com/spreadsheets/d/1p3QhVvd
 ## Analyst Landscape
 Analysts are recognizing that this sort of capability is becoming
-more a part of what's fundamentally needed for a continous delivery
+more a part of what's fundamentally needed for a continuous delivery
 platform, in order to minimize blast radius from changes. Often,
 solutions in this space are complex and hard to get up and running
 with, and they are not typically bundled or well integrated with CD

source/direction/release/release_orchestration/index.html.md

@@ -28,7 +28,7 @@ are more than welcome.
 ## Manual Processes vs. Automation
 One important consideration for how we want to implement release orchestration at
-GitLab is that we want to solve for automated, continous delivery workflows first.
+GitLab is that we want to solve for automated, continuous delivery workflows first.
 We believe that all enterprises can achieve this, and that GitLab as a whole
 is a powerful tool to unlock efficiency within DevOps. As such we avoid adding
 manual, non-automated controls to the delivery pipeline. That's not to say we don't

source/direction/secure/template.html.md.erb

@@ -105,7 +105,7 @@ performing to keep the security level to a proper level.
 ### Bill of materials
-Software is often based on many components that are reused. Every moderm programming
+Software is often based on many components that are reused. Every modern programming
 language makes easy to pull and use external libraries via package managers.
 There is a growing need to know exactly what is included in the final app, and the
 relevant information about those third-party components, like the version number,

source/gitlab-hosted/index.html.md

@@ -105,7 +105,7 @@ No, unfortunately some features are not supported on GitHost. Specifically, the
 - Grafana
 - Reply by email
 - Custom `gitlab.rb` file changes
-- Setups requiring additonal software installs
+- Setups requiring additional software installs
 ### What regions does GitHost operate in?