Merge branch 'spelling-sentence-lengths-bundle' into 'master'

Spelling sentence lengths bundle

See merge request gitlab-org/gitlab!68067

doc/.vale/gitlab/spelling-exceptions.txt

@@ -14,6 +14,7 @@ anonymized
 Ansible
 Anthos
 Apdex
+Apparmor
 approvers
 architected
 architecting
@@ -28,6 +29,7 @@ Atlassian
 auditability
 Auth0
 Authentiq
+Authy
 autocomplete
 autocompleted
 autocompletes
@@ -186,6 +188,7 @@ enum
 enums
 ETag
 Excon
+exfiltration
 expirable
 Facebook
 failover
@@ -202,6 +205,7 @@ Filebeat
 Fio
 firewalled
 firewalling
+fixup
 Flawfinder
 Flowdock
 Fluentd
@@ -246,6 +250,7 @@ Haswell
 heatmap
 heatmaps
 Helm
+Helmfile
 Heroku
 Herokuish
 Hexo

doc/administration/get_started.md

@@ -146,7 +146,7 @@ Backups of GitLab databases and filesystems are taken every 24 hours, and are ke
 - GitLab SaaS creates backups to ensure your data is secure, but you can't use these methods to export or back up your data yourself.
 - Issues are stored in the database. They can't be stored in Git itself.
 - You can use the project export option in:
-  - [The UI](../user/project/settings/import_export.md#exporting-a-project-and-its-data).
+  - [The UI](../user/project/settings/import_export.md#export-a-project-and-its-data).
   - [The API](../api/project_import_export.md#schedule-an-export).
 - [Group export](../user/group/settings/import_export.md) does *not* export the projects in it, but does export:
   - Epics

doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md

@@ -466,7 +466,7 @@ sudo gitlab-rake cache:clear
 
 ### Export a repository
 
-It's typically recommended to export a project through [the web interface](../../user/project/settings/import_export.md#exporting-a-project-and-its-data) or through [the API](../../api/project_import_export.md). In situations where this is not working as expected, it may be preferable to export a project directly via the Rails console:
+It's typically recommended to export a project through [the web interface](../../user/project/settings/import_export.md#export-a-project-and-its-data) or through [the API](../../api/project_import_export.md). In situations where this is not working as expected, it may be preferable to export a project directly via the Rails console:
 
 ```ruby
 user = User.find_by_username('USERNAME')

doc/development/import_project.md

@@ -16,7 +16,7 @@ There are several ways to import a project.
 
 ### Importing via UI
 
-The first option is to simply [import the Project tarball file via the GitLab UI](../user/project/settings/import_export.md#importing-the-project):
+The first option is to simply [import the Project tarball file via the GitLab UI](../user/project/settings/import_export.md#import-the-project):
 
 1. Create the group `qa-perf-testing`
 1. Import the [GitLab FOSS project tarball](https://gitlab.com/gitlab-org/quality/performance-data/-/blob/master/projects_export/gitlabhq_export.tar.gz) into the Group.

doc/user/admin_area/analytics/dev_ops_report.md

@@ -44,7 +44,7 @@ feature is available.
 > - DAST and SAST metrics [added](https://gitlab.com/gitlab-org/gitlab/-/issues/328033) in GitLab 14.1.
 > - Fuzz Testing metrics [added](https://gitlab.com/gitlab-org/gitlab/-/issues/330398) in GitLab 14.2.
 > - Dependency Scanning metrics [added](https://gitlab.com/gitlab-org/gitlab/-/issues/328034) in GitLab 14.2.
-> - Multiselect [added](https://gitlab.com/gitlab-org/gitlab/-/issues/333586) in GitLab 14.2.
+> - Multi-select [added](https://gitlab.com/gitlab-org/gitlab/-/issues/333586) in GitLab 14.2.
 
 DevOps Adoption shows you which groups in your organization are using the most essential features of GitLab:
 

doc/user/admin_area/settings/floc.md

@@ -8,8 +8,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60933) in GitLab Free 13.12.
 
-Federated Learning of Conhorts (FLoC) is a feature that the Chrome browser has
-rolled out, where users are categorized into different cohorts, so that
+Federated Learning of Cohorts (FLoC) is a new feature of the Chrome browser.
+It works by categorizing users into different cohorts, so that
 advertisers can use this data to uniquely target and track users. For more
 information, visit the [FLoC repository](https://github.com/WICG/floc).
 

doc/user/admin_area/settings/rate_limit_on_notes_creation.md

@@ -17,7 +17,7 @@ To change the note creation rate limit:
 1. On the left sidebar, select **Settings > Network**.
 1. Expand **Notes Rate Limits**.
 1. Under **Max requests per minute per user**, enter the new value.
-1. Optional. Under **List of users to be excluded from the limit**, list users to be excluded fromt the limit.
+1. Optional. Under **List of users to be excluded from the limit**, list users to be excluded from the limit.
 1. Select **Save changes**.
 
 This limit is:

doc/user/admin_area/settings/visibility_and_access_controls.md

@@ -211,7 +211,7 @@ You can specify from which hosting sites users can [import their projects](../..
 ## Enable project export
 
 To enable the export of
-[projects and their data](../../../user/project/settings/import_export.md#exporting-a-project-and-its-data):
+[projects and their data](../../../user/project/settings/import_export.md#export-a-project-and-its-data):
 
 1. Sign in to GitLab as a user with [Administrator role](../../permissions.md).
 1. On the top bar, select **Menu >** **{admin}** **Admin**.

doc/user/analytics/value_stream_analytics.md

@@ -124,9 +124,9 @@ From the previous example we see the time used for each stage:
 - **Issue**: 2 hrs (09:00 to 11:00)
 - **Plan**: 1 hr (11:00 to 12:00)
 - **Code**: 2 hrs (12:00 to 14:00)
-- **Test**: 5 mins
+- **Test**: 5 minutes
 - **Review**: 5 hrs (14:00 to 19:00)
-- **Staging**: 30 mins (19:00 to 19:30)
+- **Staging**: 30 minutes (19:00 to 19:30)
 
 More information:
 

doc/user/clusters/management_project_template.md

@@ -53,13 +53,13 @@ project. This image consists of a set of Bash utility scripts to support [Helm v
 This file has a list of paths to other Helmfiles for each app. They're all commented out by default, so you must uncomment
 the paths for the apps that you would like to manage.
 
-By default, each `helmfile.yaml` in these sub-paths will have the attribute `installed: true`, which signifies that everytime
-the pipeline runs, Helmfile will try to either install or update your apps according to the current state of your
-cluster and Helm releases. If you change this attribute to `installed: false`, Helmfile will try to uninstall this app
+By default, each `helmfile.yaml` in these sub-paths have the attribute `installed: true`. This signifies that every time
+the pipeline runs, Helmfile tries to either install or update your apps according to the current state of your
+cluster and Helm releases. If you change this attribute to `installed: false`, Helmfile tries try to uninstall this app
 from your cluster. [Read more](https://github.com/roboll/helmfile) about how Helmfile works.
 
 Furthermore, each app has an `applications/{app}/values.yaml` file. This is the
-place where you can define some default values for your app's Helm chart. Some apps will already have defaults
+place where you can define some default values for your app's Helm chart. Some apps already have defaults
 pre-defined by GitLab.
 
 #### Built-in applications
@@ -80,7 +80,7 @@ The [built-in supported applications](https://gitlab.com/gitlab-org/project-temp
 - [Sentry](../infrastructure/clusters/manage/management_project_applications/sentry.md)
 - [Vault](../infrastructure/clusters/manage/management_project_applications/vault.md)
 
-### Migrating from GitLab Managed Apps
+### Migrate from GitLab Managed Apps
 
 If you had GitLab Managed Apps, either One-Click or CI/CD install, read the docs on how to
 [migrate from GitLab Managed Apps to project template](migrating_from_gma_to_project_template.md)

doc/user/infrastructure/index.md

@@ -7,7 +7,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 # Infrastructure management **(FREE)**
 
 GitLab provides you with great solutions to help you manage your
-infrastrucure:
+infrastructure:
 
 - [Infrastructure as Code and GitOps](iac/index.md)
 - [Kubernetes clusters](../project/clusters/index.md)

doc/user/project/import/gitlab_com.md

@@ -15,7 +15,7 @@ To get to the importer page you need to go to "New project" page.
 
 NOTE:
 If you are interested in importing Wiki and Merge Request data to your new instance,
-you'll need to follow the instructions for [exporting a project](../settings/import_export.md#exporting-a-project-and-its-data)
+you'll need to follow the instructions for [exporting a project](../settings/import_export.md#export-a-project-and-its-data)
 
 ![New project page](img/gitlab_new_project_page_v12_2.png)
 

doc/user/project/index.md

@@ -121,7 +121,7 @@ Kubernetes, Slack, and a lot more.
   - [Bitbucket to GitLab](import/bitbucket.md)
   - [Gitea to GitLab](import/gitea.md)
   - [FogBugz to GitLab](import/fogbugz.md)
-- [Export a project from GitLab](settings/import_export.md#exporting-a-project-and-its-data)
+- [Export a project from GitLab](settings/import_export.md#export-a-project-and-its-data)
 - [Importing and exporting projects between GitLab instances](settings/import_export.md)
 
 ## GitLab Workflow - VS Code extension

doc/user/project/repository/reducing_the_repo_size_using_git.md

@@ -23,7 +23,7 @@ over [`git filter-branch`](https://git-scm.com/docs/git-filter-branch) and
 WARNING:
 Rewriting repository history is a destructive operation. Make sure to back up your repository before
 you begin. The best way back up a repository is to
-[export the project](../settings/import_export.md#exporting-a-project-and-its-data).
+[export the project](../settings/import_export.md#export-a-project-and-its-data).
 
 ## Purge files from repository history
 
@@ -44,7 +44,7 @@ To purge files from a GitLab repository:
    using a supported package manager or from source.
 
 1. Generate a fresh [export from the
-   project](../settings/import_export.html#exporting-a-project-and-its-data) and download it.
+   project](../settings/import_export.html#export-a-project-and-its-data) and download it.
    This project export contains a backup copy of your repository *and* refs
    we can use to purge files from your repository.
 

doc/user/project/settings/import_export.md

@@ -32,8 +32,8 @@ To set up a project import/export:
 
 Note the following:
 
-- Before you can import a project, you need to export the data first.
-  See [Exporting a project and its data](#exporting-a-project-and-its-data)
+- Before you can import a project, you must export the data first.
+  See [Export a project and its data](#export-a-project-and-its-data)
   for how you can export a project through the UI.
 - Imports from a newer version of GitLab are not supported.
   The Importing GitLab version must be greater than or equal to the Exporting GitLab version.
@@ -42,7 +42,7 @@ Note the following:
 - Exports are generated in your configured `shared_path`, a temporary shared directory,
   and are moved to your configured `uploads_directory`. Every 24 hours, a specific worker deletes these export files.
 - Group members are exported as project members, as long as the user has
-  maintainer or administrator access to the group where the exported project lives.
+  a maintainer or administrator role in the group where the exported project lives.
 - Project members with the [Owner role](../../permissions.md) are imported as Maintainers.
 - Imported users can be mapped by their primary email on self-managed instances, if an administrative user (not an owner) does the import.
   Otherwise, a supplementary comment is left to mention that the original author and
@@ -51,10 +51,10 @@ Note the following:
     possible through a [professional services engagement](https://about.gitlab.com/services/migration/).
 - If an imported project contains merge requests originating from forks,
   then new branches associated with such merge requests are created
-  within a project during the import/export. Thus, the number of branches
+  in a project during the import/export. Thus, the number of branches
   in the exported project could be bigger than in the original project.
 - Deploy keys allowed to push to protected branches are not exported. Therefore,
-  you need to recreate this association by first enabling these deploy keys in your
+  you must recreate this association by first enabling these deploy keys in your
   imported project and then updating your protected branches accordingly.
 
 ## Version history
@@ -141,7 +141,7 @@ NOTE:
 For more details on the specific data persisted in a project export, see the
 [`import_export.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/import_export/project/import_export.yml) file.
 
-## Exporting a project and its data
+## Export a project and its data
 
 Full project export functionality is limited to project maintainers and owners.
 You can configure such functionality through [project settings](index.md):
@@ -156,18 +156,18 @@ To export a project and its data, follow these steps:
 
    ![Export button](img/import_export_export_button.png)
 
-1. Once the export is generated, you should receive an email with a link to
+1. After the export is generated, you should receive an email with a link to
    download the file:
 
    ![Email download link](img/import_export_mail_link.png)
 
 1. Alternatively, you can come back to the project settings and download the
-   file from there, or generate a new export. Once the file is available, the page
+   file from there, or generate a new export. After the file is available, the page
    should show the **Download export** button:
 
    ![Download export](img/import_export_download_export.png)
 
-## Importing the project
+## Import the project
 
 1. The GitLab project import feature is the first import option when creating a
    new project. Click on **GitLab export**:
@@ -215,7 +215,7 @@ GitLab.com may have [different settings](../../gitlab_com/index.md#importexport)
 
 ### Import workaround for large repositories 
 
-[Maximum import size limitations](#importing-the-project)
+[Maximum import size limitations](#import-the-project)
 can prevent an import from being successful.
 If changing the import limits is not possible,
 the following local workflow can be used to temporarily

doc/user/project/settings/index.md

@@ -271,7 +271,7 @@ Enable [Service Desk](../service_desk.md) for your project to offer customer sup
 
 ### Export project
 
-Learn how to [export a project](import_export.md#importing-the-project) in GitLab.
+Learn how to [export a project](import_export.md#import-the-project) in GitLab.
 
 ### Advanced settings