Merge branch 'docs-various-typos' into 'master'

Documentation: Fix various simple typos across the codebase

See merge request gitlab-org/gitlab!44401

.gitlab/issue_templates/Migrations.md

@@ -16,7 +16,7 @@ Please add information here about why you're planning on migrating. Include any
 <!-- Please complete as many items in this list as possible. If you're not sure yet, add "TBD" (To be Decided) or "Unknown" -->
 
  * **Timeline.** - 
- * **Product.** - GitLab Gold/Ultimate or Commnunity Edition
+ * **Product.** - GitLab Gold/Ultimate or Community Edition
  * **Project's License.** What kind of OSI-approved license does your project use? 
 
 ## Current Tooling and Replacements
@@ -64,4 +64,4 @@ Here is an example of what this list might look like once populated: https://git
 ------
 
 /label ~"Open Source" ~movingtogitlab
-/cc @nuritzi 
\ No newline at end of file
+/cc @nuritzi 

.gitlab/issue_templates/Snowplow event tracking.md

@@ -8,7 +8,7 @@
  -->
 
 <!--
-We generally recommend events be tracked using a [structured event](https://docs.snowplowanalytics.com/docs/understanding-tracking-design/out-of-the-box-vs-custom-events-and-entities/#structured-events) which has 5 properties you can use. There may be instances where structured events are not sufficient. You may want to track an event where the property changes frequently or is general something very unique. In those cases, use a [self-decribing event](https://docs.snowplowanalytics.com/docs/understanding-tracking-design/out-of-the-box-vs-custom-events-and-entities/#self-describing-events)
+We generally recommend events be tracked using a [structured event](https://docs.snowplowanalytics.com/docs/understanding-tracking-design/out-of-the-box-vs-custom-events-and-entities/#structured-events) which has 5 properties you can use. There may be instances where structured events are not sufficient. You may want to track an event where the property changes frequently or is general something very unique. In those cases, use a [self-describing event](https://docs.snowplowanalytics.com/docs/understanding-tracking-design/out-of-the-box-vs-custom-events-and-entities/#self-describing-events)
 
 -->
 

app/assets/javascripts/ide/lib/languages/README.md

 # Web IDE Languages
 
 The Web IDE uses the [Monaco editor](https://microsoft.github.io/monaco-editor/) which uses the [Monarch library](https://microsoft.github.io/monaco-editor/monarch.html) for syntax highlighting. 
-The Web IDE currently supports all langauges defined in the [monaco-languages](https://github.com/microsoft/monaco-languages/tree/master/src) repository. 
+The Web IDE currently supports all languages defined in the [monaco-languages](https://github.com/microsoft/monaco-languages/tree/master/src) repository. 
 
 ## Adding New Languages
 
@@ -14,7 +14,7 @@ Should you be willing to help us and add support to GitLab for any missing langu
 2. Create a new file in this folder called `{languageName}.js`, where `{languageName}` is the name of the language you want to add support for.
 3. Follow the [Monarch documentation](https://microsoft.github.io/monaco-editor/monarch.html) to add a configuration for the new language. 
     - Example: The [`vue.js`](./vue.js) file in the current directory adds support for Vue.js Syntax Highlighting.
-4. Add tests for the new langauge implementation in `spec/frontend/ide/lib/languages/{langaugeName}.js`.
+4. Add tests for the new language implementation in `spec/frontend/ide/lib/languages/{langaugeName}.js`.
     - Example: See [`vue_spec.js`](spec/frontend/ide/lib/languages/vue_spec.js).
 5. Create a [Merge Request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) with your newly added language.
 

app/finders/README.md

@@ -19,4 +19,4 @@ Better use this:
 issues = IssuesFinder.new(project, user, filter).execute
 ```
 
-It will help keep models thiner.
+It will help keep models thinner.

app/serializers/README.md

@@ -47,11 +47,11 @@ representation. It rarely happens that a serialization entity exists without
 a corresponding domain model class. As an example, we have an `Issue` class and
 a corresponding `IssueSerializer`.
 
-Serialization entites are designed to reuse other serialization entities, which
+Serialization entities are designed to reuse other serialization entities, which
 is a convenient way to create a multi-level JSON representation of a piece of
 a domain model you want to serialize.
 
-See [documentation for Grape Entites][grape-entity-readme] for more details.
+See [documentation for Grape Entities][grape-entity-readme] for more details.
 
 ## How to implement a serializer?
 

doc/administration/gitaly/praefect.md

@@ -356,7 +356,7 @@ application server, or a Gitaly node.
    If you want to use a TLS client certificate, the options below can be used:
 
    ```ruby
-   # Connect to PostreSQL using a TLS client certificate
+   # Connect to PostgreSQL using a TLS client certificate
    # praefect['database_sslcert'] = '/path/to/client-cert'
    # praefect['database_sslkey'] = '/path/to/client-key'
 

doc/administration/troubleshooting/tracing_correlation_id.md

@@ -122,5 +122,5 @@ If you have done some horizontal scaling in your GitLab infrastructure, then
 you will need to search across _all_ of your GitLab nodes. You can do this with
 some sort of log aggregation software like Loki, ELK, Splunk, or others.
 
-You can use a tool like Ansible or PSSH (parellel SSH) that can execute identical commands across your servers in
+You can use a tool like Ansible or PSSH (parallel SSH) that can execute identical commands across your servers in
 parallel, or craft your own solution.

doc/ci/README.md

@@ -94,7 +94,7 @@ GitLab CI/CD uses a number of concepts to describe and run your build and deploy
 | [Job artifacts](pipelines/job_artifacts.md)             | Output, use, and reuse job artifacts.                                          |
 | [Cache dependencies](caching/index.md)                  | Cache your dependencies for a faster execution.                                |
 | [GitLab Runner](https://docs.gitlab.com/runner/)        | Configure your own runners to execute your scripts.                            |
-| [Pipeline efficiency](pipelines/pipeline_efficiency.md) | Configure your pipelines to run quickly and effienctly.                        |
+| [Pipeline efficiency](pipelines/pipeline_efficiency.md) | Configure your pipelines to run quickly and efficiently.                       |
 
 ## Configuration
 

doc/ci/environments/index.md

@@ -855,7 +855,7 @@ exist, you should see something like:
 
 ### Environment incident management
 
-You have successfuly setup a Continous Delivery/Deployment workflow in your project.
+You have successfully setup a Continuous Delivery/Deployment workflow in your project.
 Production environments can go down unexpectedly, including for reasons outside
 of your own control. For example, issues with external dependencies, infrastructure,
 or human error can cause major issues with an environment. This could include:

doc/development/cicd/templates.md

@@ -111,7 +111,7 @@ to include older template versions. If other templates are included with `includ
 they can be combined with the `include: remote`:
 
 ```yaml
-# To use the v13 stable template, which is not included in v14, fetch the specifc
+# To use the v13 stable template, which is not included in v14, fetch the specific
 # template from the remote template repository with the `include:remote:` keyword.
 # If you fetch from the GitLab canonical project, use the following URL format:
 # https://gitlab.com/gitlab-org/gitlab/-/raw/<version>/lib/gitlab/ci/templates/<template-name>

doc/development/database/add_foreign_key_to_existing_column.md

@@ -109,7 +109,7 @@ class RemoveRecordsWithoutUserFromEmailsTable < ActiveRecord::Migration[5.2]
   end
 
   def down
-    # Can be a no-op when data inconsistency is not affecting the pre and post deploymnet version of the application.
+    # Can be a no-op when data inconsistency is not affecting the pre and post deployment version of the application.
     # In this case we might have records in the `emails` table where the associated record in the `users` table is not there anymore.
   end
 end

doc/development/database/table_partitioning.md

@@ -85,7 +85,7 @@ ORDER BY created_at DESC
 LIMIT 100
 ```
 
-If the table is partioned on the `created_at` column the base table would
+If the table is partitioned on the `created_at` column the base table would
 look like:
 
 ```sql

doc/development/documentation/graphql_styleguide.md

@@ -78,7 +78,7 @@ You should include a link for your new document in the global navigation (the li
 left side of the documentation website). To do so, open a second MR, against the
 [GitLab documentation repository](https://gitlab.com/gitlab-org/gitlab-docs/).
 
-We store our global navgation in the [`default-nav.yaml`](https://gitlab.com/gitlab-org/gitlab-docs/-/blob/master/content/_data/default-nav.yaml) file, in the
+We store our global navigation in the [`default-nav.yaml`](https://gitlab.com/gitlab-org/gitlab-docs/-/blob/master/content/_data/default-nav.yaml) file, in the
 `content/_data` subdirectory. You can find the GraphQL section under the
 following line:
 

doc/development/feature_categorization/index.md

@@ -23,7 +23,7 @@ product categories. When this occurs, you can automatically update
 and generate a new version of the file, which needs to be committed to
 the repository.
 
-The [Scalabilitity
+The [Scalability
 team](https://about.gitlab.com/handbook/engineering/infrastructure/team/scalability/)
 currently maintains the `stages.yml` file. They will automatically be
 notified on Slack when the file becomes outdated.

doc/development/multi_version_compatibility.md

@@ -122,7 +122,7 @@ If we look at this schema from a database point of view, we can see two deployme
 And these deployments align perfectly with application changes.
 
 1. At the beginning we have `Version N` on `Schema A`.
-1. Then we have a _long_ transition periond with both `Version N` and `Version N+1` on `Schema B`.
+1. Then we have a _long_ transition period with both `Version N` and `Version N+1` on `Schema B`.
 1. When we only have `Version N+1` on `Schema B` the schema changes again.
 1. Finally we have  `Version N+1` on `Schema C`.
 

doc/development/redis.md

@@ -121,7 +121,7 @@ passing to fluentd (and ultimately Elasticsearch).
 The [Redis Keyspace
 Analyzer](https://gitlab.com/gitlab-com/gl-infra/redis-keyspace-analyzer)
 project contains tools for dumping the full key list and memory usage of a Redis
-instance, and then analyzing those lists while elimating potentially sensitive
+instance, and then analyzing those lists while eliminating potentially sensitive
 data from the results. It can be used to find the most frequent key patterns, or
 those that use the most memory.
 

doc/development/testing_guide/end_to_end/style_guide.md

@@ -141,7 +141,7 @@ end
 ```
 
 ```ruby
-Page::Project::New.peform do |new_page|
+Page::Project::New.perform do |new_page|
   new_page.do_something
 end
 ```
@@ -155,7 +155,7 @@ end
 ```
 
 ```ruby
-Page::Project::New.peform do |page|
+Page::Project::New.perform do |page|
   page.do_something
 end
 ```

doc/security/asset_proxy.md

@@ -25,7 +25,7 @@ A Camo server is used to act as the proxy.
 To install a Camo server as an asset proxy:
 
 1. Deploy a `go-camo` server. Helpful instructions can be found in
-   [building catus/go-camo](https://github.com/cactus/go-camo#building).
+   [building cactus/go-camo](https://github.com/cactus/go-camo#building).
 
 1. Make sure your instance of GitLab is running, and that you have created a private API token.
    Using the API, configure the asset proxy settings on your GitLab instance. For example:

doc/security/passwords_for_integrated_authentication_methods.md

@@ -11,4 +11,4 @@ However, to maintain data consistency, GitLab requires passwords for all user ac
 
 For such accounts, we use the [`friendly_token`](https://github.com/heartcombo/devise/blob/f26e05c20079c9acded3c0ee16da0df435a28997/lib/devise.rb#L492) method provided by the Devise gem to generate a random, unique and secure password and sets it as the account password during sign up.
 
-The length of the generated password is the set based on the value of [maximum password length](password_length_limits.md#modify-maximum-password-length-using-configuration-file) as set in the Devise configuation. The default value is 128 characters.
+The length of the generated password is the set based on the value of [maximum password length](password_length_limits.md#modify-maximum-password-length-using-configuration-file) as set in the Device configuration. The default value is 128 characters.

qa/README.md

@@ -50,7 +50,7 @@ the browser to use. You will need to have Chrome (or Chromium) and
     - [Best practices](../doc/development/testing_guide/best_practices.md)
     - [Using page objects](../doc/development/testing_guide/end_to_end/page_objects.md)
     - [Guidelines](../doc/development/testing_guide/index.md)
-    - [Tests with special setup for local environemnts](../doc/development/testing_guide/end_to_end/running_tests_that_require_special_setup.md)
+    - [Tests with special setup for local environments](../doc/development/testing_guide/end_to_end/running_tests_that_require_special_setup.md)
 
 ### Run the end-to-end tests in a local development environment