Clean up some Vale substitution warnings

Replaces some shorthand words to enforce standard

doc/administration/encrypted_configuration.md

@@ -34,4 +34,4 @@ The new secret can be generated by running:
 bundle exec rake gitlab:env:info RAILS_ENV=production GITLAB_GENERATE_ENCRYPTED_SETTINGS_KEY_BASE=true
 ```
 
-This will print general info on the GitLab instance, but will also cause the key to be generated in `<path-to-gitlab-rails>/config/secrets.yml`
+This will print general information on the GitLab instance, but will also cause the key to be generated in `<path-to-gitlab-rails>/config/secrets.yml`

doc/user/admin_area/index.md

@@ -24,7 +24,7 @@ The Admin Area is made up of the following sections:
 | Section                                        | Description                                                                                                                                                                                                                                                                              |
 |:-----------------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | **{overview}** [Overview](#overview-section)   | View your GitLab [Dashboard](#admin-dashboard), and administer [projects](#administering-projects), [users](#administering-users), [groups](#administering-groups), [jobs](#administering-jobs), [runners](#administering-runners), and [Gitaly servers](#administering-gitaly-servers). |
-| **{monitor}** Monitoring                       | View GitLab [system information](#system-info), and information on [background jobs](#background-jobs), [logs](#logs), [health checks](monitoring/health_check.md), [requests profiles](#requests-profiles), and [audit events](#audit-events).                                  |
+| **{monitor}** Monitoring                       | View GitLab [system information](#system-information), and information on [background jobs](#background-jobs), [logs](#logs), [health checks](monitoring/health_check.md), [requests profiles](#requests-profiles), and [audit events](#audit-events).                                   |
 | **{messages}** Messages                        | Send and manage [broadcast messages](broadcast_messages.md) for your users.                                                                                                                                                                                                              |
 | **{hook}** System Hooks                        | Configure [system hooks](../../system_hooks/system_hooks.md) for many events.                                                                                                                                                                                                            |
 | **{applications}** Applications                | Create system [OAuth applications](../../integration/oauth_provider.md) for integrations with other services.                                                                                                                                                                            |
@@ -37,7 +37,7 @@ The Admin Area is made up of the following sections:
 | **{lock}** Credentials **(ULTIMATE SELF)**     | View [credentials](credentials_inventory.md) that can be used to access your instance.                                                                                                                                                                                                   |
 | **{template}** Service Templates               | Create [service templates](../project/integrations/services_templates.md) for projects.                                                                                                                                                                                                  |
 | **{labels}** Labels                            | Create and maintain [labels](labels.md) for your GitLab instance.                                                                                                                                                                                                                        |
-| **{appearance}** Appearance                    | Customize [GitLab appearance](appearance.md).                                                                                                                                                                                                                                          |
+| **{appearance}** Appearance                    | Customize [GitLab appearance](appearance.md).                                                                                                                                                                                                                                            |
 | **{settings}** Settings                        | Modify the [settings](settings/index.md) for your GitLab instance.                                                                                                                                                                                                                       |
 
 ## Admin Dashboard
@@ -267,7 +267,7 @@ For each Gitaly server, the following details are listed:
 
 The following topics document the **Monitoring** section of the Admin Area.
 
-### System Info
+### System Information
 
 The **System Info** page provides the following statistics:
 
@@ -314,7 +314,7 @@ For multi-node systems we recommend ingesting the logs into services like Elasti
 | `integrations_json.log` | Activity between GitLab and integrated systems |
 | `kubernetes.log`        | Kubernetes activity |
 
-The contents of these log files can be useful when troubleshooting a problem. 
+The contents of these log files can be useful when troubleshooting a problem.
 
 For details of these log files and their contents, see [Log system](../../administration/logs.md).
 

doc/user/analytics/productivity_analytics.md

@@ -16,7 +16,7 @@ long, on average, it takes to deliver features is an enormous endeavor.
 While [Value Stream Analytics](../analytics/value_stream_analytics.md) focuses on the entire
 Software Development Life Cycle (SDLC) process, Productivity Analytics provides a way for Engineering Management to drill down in a systematic way to uncover patterns and causes for success or failure at an individual, project, or group level.
 
-Productivity can slow down for many reasons ranging from degrading code base to quickly growing teams. In order to investigate, department or team leaders can start by visualizing the time it takes for merge requests to be merged.
+Productivity can slow down for many reasons ranging from degrading codebase to quickly growing teams. In order to investigate, department or team leaders can start by visualizing the time it takes for merge requests to be merged.
 
 ## Supported features
 

doc/user/application_security/coverage_fuzzing/index.md

@@ -201,7 +201,7 @@ is a good way to balance the needs of letting a developer's per-commit pipeline
 and also giving the fuzzer a large amount of time to fully explore and test the app.
 
 Long-running fuzzing jobs are usually necessary for the coverage guided fuzzer to find deeper bugs
-in your latest code base. THe following is an example of what `.gitlab-ci.yml` looks like in this
+in your latest codebase. THe following is an example of what `.gitlab-ci.yml` looks like in this
 workflow (for the full example, see the [repository](https://gitlab.com/gitlab-org/security-products/demos/coverage-fuzzing/go-fuzzing-example/-/tree/continuous_fuzzing)):
 
 ```yaml

doc/user/application_security/vulnerability_report/index.md

@@ -52,7 +52,7 @@ You can also dismiss vulnerabilities in the table:
 
 The vulnerabilities that exist in your project's
 [default branch](../../project/repository/branches/index.md#default-branch) are accessed by navigating to
-**Security & Compliance > Vulnerability Report**. 
+**Security & Compliance > Vulnerability Report**.
 
 The project vulnerability report first displays the time at which the last pipeline completed on the project's
 default branch. There's also a link to view this in more detail. In the case of any pipeline failures,
@@ -83,7 +83,7 @@ The fields in the export include:
 - Status
 - Vulnerability
 - Details
-- Additional Info
+- Additional Information
 - Severity
 - [CVE](https://cve.mitre.org/) (Common Vulnerabilities and Exposures)
 - [CWE](https://cwe.mitre.org/) (Common Weakness Enumeration)

doc/user/feature_flags.md

@@ -29,11 +29,11 @@ GitLab.com. To see the full notes:
 
 1. Click the three-dots icon (ellipsis) to expand version history notes:
 
-   ![Version history note with FF info](img/version_history_notes_collapsed_v13_2.png)
+   ![Version history note with FF information](img/version_history_notes_collapsed_v13_2.png)
 
 1. Read the version history information:
 
-   ![Version history note with FF info](img/feature_flags_history_note_info_v13_2.png)
+   ![Version history note with FF information](img/feature_flags_history_note_info_v13_2.png)
 
 If you're a user of a GitLab self-managed instance and you want to try to use a
 disabled feature, you can ask a [GitLab administrator to enable it](../administration/feature_flags.md),

doc/user/packages/generic_packages/index.md

@@ -48,7 +48,7 @@ PUT /projects/:id/packages/generic/:package_name/:package_version/:file_name
 | `id`               | integer/string  | yes      | The ID or [URL-encoded path of the project](../../../api/README.md#namespaced-path-encoding).                                              |
 | `package_name`     | string          | yes      | The package name. It can contain only lowercase letters (`a-z`), uppercase letter (`A-Z`), numbers (`0-9`), dots (`.`), hyphens (`-`), or underscores (`_`).
 | `package_version`  | string          | yes      | The package version. It can contain only numbers (`0-9`), and dots (`.`). Must be in the format of `X.Y.Z`, i.e. should match `/\A\d+\.\d+\.\d+\z/` regular expression.
-| `file_name`        | string          | yes      | The file name. It can contain only lowercase letters (`a-z`), uppercase letter (`A-Z`), numbers (`0-9`), dots (`.`), hyphens (`-`), or underscores (`_`).
+| `file_name`        | string          | yes      | The filename. It can contain only lowercase letters (`a-z`), uppercase letter (`A-Z`), numbers (`0-9`), dots (`.`), hyphens (`-`), or underscores (`_`).
 
 Provide the file context in the request body.
 
@@ -87,7 +87,7 @@ GET /projects/:id/packages/generic/:package_name/:package_version/:file_name
 | `id`               | integer/string  | yes      | The ID or [URL-encoded path of the project](../../../api/README.md#namespaced-path-encoding). |
 | `package_name`     | string          | yes      | The package name.                                                                   |
 | `package_version`  | string          | yes      | The package version.                                                                |
-| `file_name`        | string          | yes      | The file name.                                                                      |
+| `file_name`        | string          | yes      | The filename.                                                                      |
 
 The file context is served in the response body. The response content type is `application/octet-stream`.