Merge branch 'spelling-fixes' into 'master'

Spelling fixes

See merge request gitlab-org/gitlab!70492

doc/administration/gitaly/praefect.md

@@ -275,7 +275,7 @@ you need to prepare PostgreSQL server with [setup instruction](#manual-database-
 
 ```ruby
 pgbouncer['databases'] = {
-  # Other database configuation including gitlabhq_production
+  # Other database configuration including gitlabhq_production
   ...
 
   praefect_production: {

doc/administration/operations/puma.md

@@ -70,7 +70,7 @@ restarting the workers. `per_worker_max_memory_mb` should be set to a
 higher value if the worker killer is replacing workers too often.
 
 Worker count is calculated based on CPU cores, so a small GitLab deployment
-wih 4-8 workers may experience performance issues if workers are being restarted
+with 4-8 workers may experience performance issues if workers are being restarted
 frequently, once or more per minute. This is too often.
 
 A higher value of `1200` or more would be beneficial if the server has free memory.

doc/administration/redis/troubleshooting.md

@@ -73,7 +73,7 @@ there may be something wrong with your configuration files or it can be related
 to [this issue](https://github.com/redis/redis-rb/issues/531).
 
 You must make sure you are defining the same value in `redis['master_name']`
-and `redis['master_pasword']` as you defined for your sentinel node.
+and `redis['master_password']` as you defined for your sentinel node.
 
 The way the Redis connector `redis-rb` works with sentinel is a bit
 non-intuitive. We try to hide the complexity in omnibus, but it still requires

doc/administration/reference_architectures/troubleshooting.md

@@ -158,7 +158,7 @@ there may be something wrong with your configuration files or it can be related
 to [this issue](https://github.com/redis/redis-rb/issues/531).
 
 You must make sure you are defining the same value in `redis['master_name']`
-and `redis['master_pasword']` as you defined for your sentinel node.
+and `redis['master_password']` as you defined for your sentinel node.
 
 The way the Redis connector `redis-rb` works with sentinel is a bit
 non-intuitive. We try to hide the complexity in omnibus, but it still requires

doc/ci/environments/index.md

@@ -730,7 +730,7 @@ the `review/feature-1` spec takes precedence over `review/*` and `*` specs.
 
 ### Rename an environment
 
-> Renaming environments through the UI was [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/68550) in GitLab 14.3. Renaming environments through the API was deprected and [will be removed](https://gitlab.com/gitlab-org/gitlab/-/issues/338897) in GitLab 15.0.
+> Renaming environments through the UI was [removed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/68550) in GitLab 14.3. Renaming environments through the API was deprecated and [will be removed](https://gitlab.com/gitlab-org/gitlab/-/issues/338897) in GitLab 15.0.
 
 Renaming an environment through the UI is not possible.
 Instead, you need to delete the old environment and create a new one:

doc/development/database/pagination_guidelines.md

@@ -302,7 +302,7 @@ LIMIT 20
 
 ##### Tooling
 
-A generic keyset pagination library is available within the GitLab project which can most of the cases easly replace the existing, kaminari based pagination with significant performance improvements when dealing with large datasets.
+A generic keyset pagination library is available within the GitLab project which can most of the cases easily replace the existing, kaminari based pagination with significant performance improvements when dealing with large datasets.
 
 Example:
 

doc/development/experiment_guide/experimentation.md

@@ -106,7 +106,7 @@ class SomeWorker
 
     # Since we cannot access cookies in a worker, we need to bucket models
     # based on a unique, unchanging attribute instead.
-    # It is therefore necessery to always provide the same subject.
+    # It is therefore necessary to always provide the same subject.
     if Gitlab::Experimentation.in_experiment_group?(:experiment_key, subject: user)
       # execute experimental code
     else

doc/development/fe_guide/graphql.md

@@ -458,7 +458,7 @@ export default {
 };
 ```
 
-Note that, even if the directive evalutes to `false`, the guarded entity is sent to the backend and
+Note that, even if the directive evaluates to `false`, the guarded entity is sent to the backend and
 matched against the GraphQL schema. So this approach requires that the feature-flagged entity
 exists in the schema, even if the feature flag is disabled. When the feature flag is turned off, it
 is recommended that the resolver returns `null` at the very least.
@@ -484,7 +484,7 @@ export default {
 This approach is not recommended as it results in bigger merge requests and requires maintaining
 two similar queries for as long as the feature flag exists. This can be used in cases where the new
 GraphQL entities are not yet part of the schema, or if they are feature-flagged at the schema level
-(`new_entitiy: :feature_flag`).
+(`new_entity: :feature_flag`).
 
 ### Manually triggering queries
 
@@ -1340,7 +1340,7 @@ describe('when query times out', () => {
     expect(getAlert().exists()).toBe(false);
     expect(getGraph().exists()).toBe(true);
 
-    /* fails again, alert retuns but data persists */
+    /* fails again, alert returns but data persists */
     await advanceApolloTimers();
     expect(getAlert().exists()).toBe(true);
     expect(getGraph().exists()).toBe(true);

doc/development/import_project.md

@@ -195,7 +195,7 @@ You can use this snippet: `https://gitlab.com/gitlab-org/gitlab/snippets/1924954
 You can execute the script from the `gdk/gitlab` directory like this:
 
 ```shell
-bundle exec rails r  /path_to_sript/script.rb project_name /path_to_extracted_project request_store_enabled
+bundle exec rails r  /path_to_script/script.rb project_name /path_to_extracted_project request_store_enabled
 ```
 
 ## Troubleshooting

doc/development/internal_api.md

@@ -510,7 +510,7 @@ create a single vulnerability.
 | Attribute       | Type   | Required | Description |
 |:----------------|:-------|:---------|:------------|
 | `vulnerability` | Hash   | yes      | Vulnerability data matching the security report schema [`vulnerability` field](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/blob/master/src/security-report-format.json). |
-| `scanner`       | Hash   | yes      | Scanner data matching the security report schmea [`scanner` field](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/blob/master/src/security-report-format.json). |
+| `scanner`       | Hash   | yes      | Scanner data matching the security report schema [`scanner` field](https://gitlab.com/gitlab-org/security-products/security-report-schemas/-/blob/master/src/security-report-format.json). |
 
 ```plaintext
 PUT internal/kubernetes/modules/starboard_vulnerability

doc/development/multi_version_compatibility.md

@@ -201,7 +201,7 @@ gantt
   section Database
     Schema A      :done, schemaA, 00:00  , 1h
     Schema B      :crit, schemaB, after migr, 58m
-    Schema C.     : schmeaC, after postmigr, 1h
+    Schema C.     : schemaC, after postmigr, 1h
 
   section Machine A
     Version N      :done, mavn, 00:00 , 75m

doc/development/transient/prevention-patterns.md

@@ -97,7 +97,7 @@ by the server-side endpoint satisfies the API contract.
 #### Related reading
 
 [Debug it!](https://pragprog.com/titles/pbdp/debug-it/) explores techniques to diagnose
-and fix non-determinstic bugs and write software that is easier to debug.
+and fix non-deterministic bugs and write software that is easier to debug.
 
 ## Backend
 

doc/install/aws/index.md

@@ -43,7 +43,7 @@ GitLab implementation patterns build upon [GitLab Reference Architectures](../..
 
 Testing-backed architectural qualification is a fundamental concept behind implementation patterns:
 
-- Implementation patterns maintain GitLab Reference Architecture compliance and provide [GitLab Performance Tool](https://gitlab.com/gitlab-org/quality/performance) (gpt) reports to demonstrate adherance to them.
+- Implementation patterns maintain GitLab Reference Architecture compliance and provide [GitLab Performance Tool](https://gitlab.com/gitlab-org/quality/performance) (gpt) reports to demonstrate adherence to them.
 - Implementation patterns may be qualified by and/or contributed to by the technology vendor. For instance, an implementation pattern for AWS may be officially reviewed by AWS.
 - Implementation patterns may specify and test Cloud Platform PaaS services for suitability for GitLab. This testing can be coordinated and help qualify these technologies for Reference Architectures. For instance, qualifying compatibility with and availability of runtime versions of top level PaaS such as those for PostgreSQL and Redis.
 - Implementation patterns can provided qualified testing for platform limitations, for example, ensuring Gitaly Cluster can work correctly on specific Cloud Platform availability zone latency and throughput characteristics or qualifying what levels of available platform partner local disk performance is workable for Gitaly server to operate with integrity.

doc/integration/recaptcha.md

@@ -24,7 +24,7 @@ To use reCAPTCHA, first you must create a site and private key.
 1. To enable reCAPTCHA for logins via password, select the **Enable reCAPTCHA for login** checkbox.
 1. Save the configuration.
 1. Change the first line of the `#execute` method in `app/services/spam/spam_verdict_service.rb`
-   to `return CONDITONAL_ALLOW` so that the spam check short-circuits and triggers the response to
+   to `return CONDITIONAL_ALLOW` so that the spam check short-circuits and triggers the response to
    return `recaptcha_html`.
 
 NOTE:

doc/operations/error_tracking.md

@@ -50,7 +50,7 @@ You may also want to enable Sentry's GitLab integration by following the steps i
 ### Enable GitLab Runner
 
 To configure GitLab Runner with Sentry, you must add the value for `sentry_dsn` to your GitLab
-Runner's `config.toml` configuration file, as referenced in [GitLab Runner Advanced Configuraton](https://docs.gitlab.com/runner/configuration/advanced-configuration.html).
+Runner's `config.toml` configuration file, as referenced in [GitLab Runner Advanced Configuration](https://docs.gitlab.com/runner/configuration/advanced-configuration.html).
 While setting up Sentry, select **Go** if you're asked for the project type.
 
 If you see the following error in your GitLab Runner logs, then you should specify the deprecated

doc/topics/autodevops/customize.md

@@ -464,7 +464,7 @@ The following table lists variables used to disable jobs.
 | `license_scanning`                     | `LICENSE_MANAGEMENT_DISABLED`   | [From GitLab 12.8](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/22773) | If the variable is present, the job isn't created. |
 | `load_performance`                     | `LOAD_PERFORMANCE_DISABLED`     | From GitLab 13.2      | If the variable is present, the job isn't created. |
 | `nodejs-scan-sast`                     | `SAST_DISABLED`                 |                       | If the variable is present, the job isn't created. |
-| `performance`                          | `PERFORMANCE_DISABLED`          | GitLab 11.0 to GitLab 13.12 | Browser performance. If the variable is present, the job isn't created. Replaced by `browser_peformance`. |
+| `performance`                          | `PERFORMANCE_DISABLED`          | GitLab 11.0 to GitLab 13.12 | Browser performance. If the variable is present, the job isn't created. Replaced by `browser_performance`. |
 | `browser_performance`                  | `BROWSER_PERFORMANCE_DISABLED`  | From GitLab 14.0      | Browser performance. If the variable is present, the job isn't created. Replaces `performance`. |
 | `phpcs-security-audit-sast`            | `SAST_DISABLED`                 |                       | If the variable is present, the job isn't created. |
 | `pmd-apex-sast`                        | `SAST_DISABLED`                 |                       | If the variable is present, the job isn't created. |

doc/update/plan_your_upgrade.md

@@ -88,7 +88,7 @@ To restore your GitLab backup:
 
 - Before restoring, make sure to read about the
   [prerequisites](../raketasks/backup_restore.md#restore-gitlab), most importantly,
-  the versions of the backed up and the new GitLab istance must be the same.
+  the versions of the backed up and the new GitLab instance must be the same.
 - [Restore GitLab](../raketasks/backup_restore.md#restore-gitlab).
   Make sure to follow the instructions based on your installation method.
   Confirm that the [secrets and configuration files](../raketasks/backup_restore.md#storing-configuration-files) are also restored.

doc/user/application_security/dependency_scanning/index.md

@@ -295,7 +295,7 @@ variation of this file (for example, `requirements.pip` or `requires.txt`).
 #### Java and Scala
 
 We only execute one build in the directory where a build file has been detected, such as `build.sbt` or `build.gradle`.
-Please note, we support the following types of Java project stuctures:
+Please note, we support the following types of Java project structures:
 
 - [multi-project sbt builds](https://www.scala-sbt.org/1.x/docs/Multi-Project.html)
 - [multi-project gradle builds](https://docs.gradle.org/current/userguide/intro_multi_project_builds.html)

doc/user/application_security/policies/index.md

@@ -396,7 +396,7 @@ In this example:
   and `Site Profile D`.
 - Secret detection and container scanning scans run for every pipeline executed on the `main` branch.
 - Cluster Image Scanning scan runs every 24h. The scan runs on the `production-cluster` cluster and fetches vulnerabilities
-  from the container with the name `database` configured for deployment with the name `production-application` in the `production-namepsace` namespace.
+  from the container with the name `database` configured for deployment with the name `production-application` in the `production-namespace` namespace.
 
 ## Roadmap
 

doc/user/gitlab_com/index.md

@@ -14,7 +14,7 @@ This page contains information about the settings that are used on GitLab.com, a
 GitLab.com has the following requirements for passwords on new accounts and password changes:
 
 - Minimum character length 8 characters.
-- Maximum character lenght 128 characters.
+- Maximum character length 128 characters.
 - All characters are accepted. For example, `~`, `!`, `@`, `#`, `$`, `%`, `^`, `&`, `*`, `()`,
   `[]`, `_`, `+`,  `=`, and `-`.
 

doc/user/group/saml_sso/index.md

@@ -337,7 +337,7 @@ Ensure your SAML identity provider sends an attribute statement named `Groups` o
 
 NOTE:
 To inspect the SAML response, you can use one of these [SAML debugging tools](#saml-debugging-tools).
-Also note that the value for `Groups` or `groups` in the SAML reponse can be either the group name or
+Also note that the value for `Groups` or `groups` in the SAML response can be either the group name or
 the group ID depending what the IdP sends to GitLab.
 
 When SAML SSO is enabled for the top-level group, `Maintainer` and `Owner` level users

doc/user/project/clusters/add_eks_clusters.md

@@ -10,7 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 > - [Deprecated](https://gitlab.com/gitlab-org/gitlab/-/issues/327908) in GitLab 14.0.
 
 WARNING:
-Use [Infrastrucure as Code](../../infrastructure/index.md) to create new clusters. The method described in this document is deprecated as of GitLab 14.0.
+Use [Infrastructure as Code](../../infrastructure/index.md) to create new clusters. The method described in this document is deprecated as of GitLab 14.0.
 
 Through GitLab, you can create new clusters and add existing clusters hosted on Amazon Elastic
 Kubernetes Service (EKS).

doc/user/project/clusters/add_gke_clusters.md

@@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 > - [Deprecated](https://gitlab.com/groups/gitlab-org/-/epics/6049) in GitLab 14.0.
 
 WARNING:
-Use [Infrastrucure as Code](../../infrastructure/index.md) to create new clusters. The method described in this document is deprecated as of GitLab 14.0.
+Use [Infrastructure as Code](../../infrastructure/index.md) to create new clusters. The method described in this document is deprecated as of GitLab 14.0.
 
 Through GitLab, you can create new clusters and add existing clusters hosted on Amazon Elastic
 Kubernetes Service (EKS).

doc/user/project/clusters/add_remove_clusters.md

@@ -53,7 +53,7 @@ supports connecting existing clusters using the certificate-based connection met
 As of GitLab 14.0, use the [GitLab Kubernetes Agent](../../clusters/agent/index.md)
 to connect your cluster to GitLab.
 
-Alternativelly, you can [add an existing cluster](add_existing_cluster.md)
+Alternatively, you can [add an existing cluster](add_existing_cluster.md)
 through the certificate-based method, but we don't recommend using this method for [security implications](../../infrastructure/clusters/connect/index.md#security-implications-for-clusters-connected-with-certificates).
 
 ## Configure your cluster

doc/user/project/deploy_tokens/index.md

@@ -181,7 +181,7 @@ To pull images from the Dependency Proxy, you must:
 
 1. Create a group deploy token with both `read_registry` and `write_registry` scopes.
 1. Take note of your `username` and `token`.
-1. Follow the Depenency Proxy [authentication instructions](../../packages/dependency_proxy/index.md).
+1. Follow the Dependency Proxy [authentication instructions](../../packages/dependency_proxy/index.md).
 
 ### GitLab deploy token
 

doc/user/project/settings/index.md

@@ -179,7 +179,7 @@ cannot change them:
 - Explicitly set the container image file to run the job in. This ensures that your script
   steps execute in the correct environment.
 - Explicitly set any relevant GitLab pre-defined [job keywords](../../../ci/yaml/index.md#job-keywords).
-  This ensures that your job uses the settings you intend and that they are not overriden by
+  This ensures that your job uses the settings you intend and that they are not overridden by
   project-level pipelines.
 
 ### Sharing and permissions