Merge branch 'eread/change-info-to-information' into 'master'

Changes most instances of info to information

See merge request gitlab-org/gitlab!28986

doc/.vale/gitlab/Substitutions.yml

@@ -14,4 +14,3 @@ swap:
   postgres: PostgreSQL
   self hosted: self-managed
   self-hosted: self-managed
-  

doc/administration/auth/how_to_configure_ldap_gitlab_ee/index.md

@@ -44,7 +44,7 @@ _The reporter permission allows support staff to manage issues, labels, and revi
 
 > Guest permissions allows people ops staff to review and lodge new issues while allowing no read or write access to project code or [confidential issues](../../../user/project/issues/confidential_issues.md#permissions-and-access-to-confidential-issues) created by other users.
 
-See the [permission list](../../../user/permissions.md) for complementary info.
+See the [permission list](../../../user/permissions.md) for complementary information.
 
 #### Group permissions - example
 

doc/administration/high_availability/README.md

@@ -273,7 +273,7 @@ On different cloud vendors a best effort like for like can be used.
 
 [^8]: The architectures were built and tested with the [Intel Xeon E5 v3 (Haswell)](https://cloud.google.com/compute/docs/cpu-platforms)
       CPU platform on GCP. On different hardware you may find that adjustments, either lower
-      or higher, are required for your CPU or Node counts accordingly. For more info a
+      or higher, are required for your CPU or Node counts accordingly. For more information, a
       [Sysbench](https://github.com/akopytov/sysbench) benchmark of the CPU can be found
       [here](https://gitlab.com/gitlab-org/quality/performance/-/wikis/Reference-Architectures/GCP-CPU-Benchmarks).
 

doc/administration/troubleshooting/diagnostics_tools.md

@@ -13,7 +13,7 @@ before attempting to use these tools.
 ## gitlabsos
 
 The [gitlabsos](https://gitlab.com/gitlab-com/support/toolbox/gitlabsos/) utility
-provides a unified method of gathering info and logs from GitLab and the system it's
+provides a unified method of gathering information and logs from GitLab and the system it's
 running on.
 
 ## strace-parser

doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md

@@ -751,7 +751,7 @@ This content has been moved to the [Troubleshooting Sidekiq docs](./sidekiq.md).
 
 ## LFS
 
-### Get info about LFS objects and associated project
+### Get information about LFS objects and associated project
 
 ```ruby
 o=LfsObject.find_by(oid: "<oid>")

doc/administration/troubleshooting/kubernetes_cheat_sheet.md

@@ -168,7 +168,7 @@ and they will assist you with any issues you are having.
   kubectl exec -it <task-runner-pod-name> -- /srv/gitlab/bin/rails dbconsole -p
   ```
 
-- How to get info about Helm installation status:
+- How to get information about Helm installation status:
 
   ```shell
   helm status name-of-installation
@@ -199,7 +199,7 @@ and they will assist you with any issues you are having.
     helm upgrade <release name> <chart path> -f gitlab.yaml
     ```
 
-- How to get the manifest for a release. It can be useful because it contains the info about
+- How to get the manifest for a release. It can be useful because it contains the information about
 all Kubernetes resources and dependent charts:
 
   ```shell

doc/api/graphql/index.md

@@ -72,7 +72,7 @@ Root-level queries are defined in
 
 GitLab supports batching queries into a single request using
 [apollo-link-batch-http](https://www.apollographql.com/docs/link/links/batch-http/). More
-info about multiplexed queries is also available for
+information about multiplexed queries is also available for
 [graphql-ruby](https://graphql-ruby.org/queries/multiplex.html) the
 library GitLab uses on the backend.
 

doc/api/oauth2.md

@@ -102,7 +102,7 @@ CAUTION: **Important:**
 Avoid using this flow for applications that store data outside of the GitLab
 instance. If you do, make sure to verify `application id` associated with the
 access token before granting access to the data
-(see [`/oauth/token/info`](#retrieving-the-token-info)).
+(see [`/oauth/token/info`](#retrieving-the-token-information)).
 
 Unlike the web flow, the client receives an `access token` immediately as a
 result of the authorization request. The flow does not use the client secret
@@ -213,7 +213,7 @@ or you can put the token to the Authorization header:
 curl --header "Authorization: Bearer OAUTH-TOKEN" https://gitlab.example.com/api/v4/user
 ```
 
-## Retrieving the Token Info
+## Retrieving the token information
 
 To verify the details of a token, use the `token/info` endpoint provided by the Doorkeeper gem.
 For more information, see [`/oauth/token/info`](https://github.com/doorkeeper-gem/doorkeeper/wiki/API-endpoint-descriptions-and-examples#get----oauthtokeninfo).

doc/api/repository_files.md

@@ -82,7 +82,7 @@ X-Gitlab-Size: 1476
 
 ## Get file blame from repository
 
-Allows you to receive blame information. Each blame range contains lines and corresponding commit info.
+Allows you to receive blame information. Each blame range contains lines and corresponding commit information.
 
 ```plaintext
 GET /projects/:id/repository/files/:file_path/blame

doc/api/v3_to_v4.md

@@ -67,7 +67,7 @@ Below are the changes made between V3 and V4.
 - Remove `GET /groups/owned`. Use `GET /groups?owned=true` instead [!9505](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9505)
 - Return 202 with JSON body on async removals on V4 API (`DELETE /projects/:id/repository/merged_branches` and `DELETE /projects/:id`) [!9449](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9449)
 - `GET /projects/:id/milestones?iid[]=x&iid[]=y` array filter has been renamed to `iids` [!9096](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9096)
-- Return basic info about pipeline in `GET /projects/:id/pipelines` [!8875](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/8875)
+- Return basic information about pipeline in `GET /projects/:id/pipelines` [!8875](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/8875)
 - Renamed all `build` references to `job` [!9463](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9463)
 - Drop `GET /projects/:id/repository/commits/:sha/jobs` [!9463](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9463)
 - Rename Build Triggers to be Pipeline Triggers API [!9713](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/9713)

doc/ci/docker/using_docker_images.md

@@ -532,7 +532,7 @@ runtime.
 
 There are two approaches that you can take in order to access a
 private registry. Both require setting the environment variable
-`DOCKER_AUTH_CONFIG` with appropriate authentication info.
+`DOCKER_AUTH_CONFIG` with appropriate authentication information.
 
 1. Per-job: To configure one job to access a private registry, add
    `DOCKER_AUTH_CONFIG` as a job variable.

doc/development/api_graphql_styleguide.md

@@ -150,7 +150,7 @@ query($project_path: ID!) {
 ```
 
 This would return the first 2 pipelines of a project and related
-pagination info., ordered by descending ID. The returned data would
+pagination information, ordered by descending ID. The returned data would
 look like this:
 
 ```json

doc/development/documentation/site_architecture/global_nav.md

@@ -272,7 +272,7 @@ and the following syntax rules.
 - For `index.html` files, use the clean (canonical) URL: `path/to/`.
 - For EE-only docs, use the same relative path, but add the attribute `ee_only: true` below
   the `doc_url` or `category_url`, as explained above. This displays
-  an "info" icon on the nav to make the user aware that the feature is
+  an "information" icon on the nav to make the user aware that the feature is
   EE-only.
 
 DANGER: **Important!**

doc/development/documentation/styleguide.md

@@ -583,7 +583,7 @@ For other punctuation rules, please refer to the
 - [Avoid using symbols and special chars](https://gitlab.com/gitlab-org/gitlab-docs/issues/84)
   in headers. Whenever possible, they should be plain and short text.
 - Avoid adding things that show ephemeral statuses. For example, if a feature is
-  considered beta or experimental, put this info in a note, not in the heading.
+  considered beta or experimental, put this information in a note, not in the heading.
 - When introducing a new document, be careful for the headings to be
   grammatically and syntactically correct. Mention an [assigned technical writer (TW)](https://about.gitlab.com/handbook/product/categories/)
   for review.

doc/development/emails.md

@@ -17,7 +17,7 @@ dummy data.
 The previews live in [`app/mailers/previews`][previews] and can be viewed at
 [`/rails/mailers`](http://localhost:3000/rails/mailers).
 
-See the [Rails guides](https://guides.rubyonrails.org/action_mailer_basics.html#previewing-emails) for more info.
+See the [Rails guides](https://guides.rubyonrails.org/action_mailer_basics.html#previewing-emails) for more information.
 
 [previews]: https://gitlab.com/gitlab-org/gitlab-foss/tree/master/app/mailers/previews
 

doc/development/fe_guide/style/scss.md

@@ -264,7 +264,7 @@ Note that this won't fix every problem, but it should fix a majority.
 ### Ignoring issues
 
 If you want a line or set of lines to be ignored by the linter, you can use
-`// scss-lint:disable RuleName` ([more info](https://github.com/sds/scss-lint#disabling-linters-via-source)):
+`// scss-lint:disable RuleName` ([more information](https://github.com/sds/scss-lint#disabling-linters-via-source)):
 
 ```scss
 // This lint rule is disabled because it is supported only in Chrome/Safari

doc/integration/saml.md

@@ -370,14 +370,14 @@ You may also bypass the auto signin feature by browsing to
 >**Note:**
 This setting is only available on GitLab 8.6 and above.
 This setting should only be used to map attributes that are part of the
-OmniAuth info hash schema.
+OmniAuth `info` hash schema.
 
 `attribute_statements` is used to map Attribute Names in a SAMLResponse to entries
-in the OmniAuth [info hash](https://github.com/omniauth/omniauth/wiki/Auth-Hash-Schema#schema-10-and-later).
+in the OmniAuth [`info` hash](https://github.com/omniauth/omniauth/wiki/Auth-Hash-Schema#schema-10-and-later).
 
 For example, if your SAMLResponse contains an Attribute called 'EmailAddress',
 specify `{ email: ['EmailAddress'] }` to map the Attribute to the
-corresponding key in the info hash. URI-named Attributes are also supported, e.g.
+corresponding key in the `info` hash. URI-named Attributes are also supported, e.g.
 `{ email: ['http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress'] }`.
 
 This setting allows you tell GitLab where to look for certain attributes required

doc/integration/shibboleth.md

@@ -8,7 +8,7 @@ In order to enable Shibboleth support in GitLab we need to use Apache instead of
 
 To enable the Shibboleth OmniAuth provider you must configure Apache Shibboleth module.
 The installation and configuration of the module itself is out of the scope of this document.
-Check <https://wiki.shibboleth.net/confluence/display/SP3/Apache> for more info.
+Check <https://wiki.shibboleth.net/confluence/display/SP3/Apache> for more information.
 
 You can find Apache config in [GitLab Recipes](https://gitlab.com/gitlab-org/gitlab-recipes/tree/master/web-server/apache).
 

doc/security/crime_vulnerability.md

@@ -4,12 +4,11 @@ type: reference
 
 # How we manage the TLS protocol CRIME vulnerability
 
-> CRIME ("Compression Ratio Info-leak Made Easy") is a security exploit against
+[CRIME](https://en.wikipedia.org/w/index.php?title=CRIME&oldid=692423806) is a security exploit against
 secret web cookies over connections using the HTTPS and SPDY protocols that also
 use data compression. When used to recover the content of secret
 authentication cookies, it allows an attacker to perform session hijacking on an
 authenticated web session, allowing the launching of further attacks.
-([CRIME](https://en.wikipedia.org/w/index.php?title=CRIME&oldid=692423806))
 
 ## Description
 

doc/topics/git/numerous_undo_possibilities_in_git/index.md

@@ -14,7 +14,7 @@ In this tutorial, we will show you different ways of undoing your work in Git, f
 we will assume you have a basic working knowledge of. Check GitLab's
 [Git documentation](../index.md) for reference.
 
-Also, we will only provide some general info of the commands, which is enough
+Also, we will only provide some general information of the commands, which is enough
 to get you started for the easy cases/examples, but for anything more advanced
 please refer to the [Git book](https://git-scm.com/book/en/v2).
 

doc/user/admin_area/settings/continuous_integration.md

@@ -116,7 +116,7 @@ Once saved, you can see the build quota in the group admin view.
 The quota can also be viewed in the project admin view if shared Runners
 are enabled.
 
-![Project admin info](img/admin_project_quota_view.png)
+![Project admin information](img/admin_project_quota_view.png)
 
 You can see an overview of the pipeline minutes quota of all projects of
 a group in the **Usage Quotas** page available to the group page settings list.

doc/user/application_security/container_scanning/index.md

@@ -367,8 +367,8 @@ the report JSON unless stated otherwise. Presence of optional fields depends on
 | `vulnerabilities[].message`                          | A short text that describes the vulnerability, it may include occurrence's specific information. Optional.                                                                                                                                                                                                                                                                                 |
 | `vulnerabilities[].description`                      | A long text that describes the vulnerability. Optional.                                                                                                                                                                                                                                                                                                                                    |
 | `vulnerabilities[].cve`                              | A fingerprint string value that represents a concrete occurrence of the vulnerability. It's used to determine whether two vulnerability occurrences are same or different. May not be 100% accurate. **This is NOT a [CVE](https://cve.mitre.org/)**.                                                                                                                                      |
-| `vulnerabilities[].severity`                         | How much the vulnerability impacts the software. Possible values: `Undefined` (an analyzer has not provided this info), `Info`, `Unknown`, `Low`, `Medium`, `High`, `Critical`.  **Note:** Our current container scanning tool based on [klar](https://github.com/optiopay/klar) only provides the following levels: `Unknown`, `Low`, `Medium`, `High`, `Critical`.                       |
-| `vulnerabilities[].confidence`                       | How reliable the vulnerability's assessment is. Possible values: `Undefined` (an analyzer has not provided this info), `Ignore`, `Unknown`, `Experimental`, `Low`, `Medium`, `High`, `Confirmed`.  **Note:** Our current container scanning tool based on [klar](https://github.com/optiopay/klar) does not provide a confidence level, so this value is currently hardcoded to `Unknown`. |
+| `vulnerabilities[].severity`                         | How much the vulnerability impacts the software. Possible values: `Undefined` (an analyzer has not provided this information), `Info`, `Unknown`, `Low`, `Medium`, `High`, `Critical`.  **Note:** Our current container scanning tool based on [klar](https://github.com/optiopay/klar) only provides the following levels: `Unknown`, `Low`, `Medium`, `High`, `Critical`.                       |
+| `vulnerabilities[].confidence`                       | How reliable the vulnerability's assessment is. Possible values: `Undefined` (an analyzer has not provided this information), `Ignore`, `Unknown`, `Experimental`, `Low`, `Medium`, `High`, `Confirmed`.  **Note:** Our current container scanning tool based on [klar](https://github.com/optiopay/klar) does not provide a confidence level, so this value is currently hardcoded to `Unknown`. |
 | `vulnerabilities[].solution`                         | Explanation of how to fix the vulnerability. Optional.                                                                                                                                                                                                                                                                                                                                     |
 | `vulnerabilities[].scanner`                          | A node that describes the analyzer used to find this vulnerability.                                                                                                                                                                                                                                                                                                                        |
 | `vulnerabilities[].scanner.id`                       | Id of the scanner as a snake_case string.                                                                                                                                                                                                                                                                                                                                                  |

doc/user/application_security/dependency_scanning/index.md

@@ -365,8 +365,8 @@ the report JSON unless stated otherwise. Presence of optional fields depends on
 | `vulnerabilities[].message`                          | A short text that describes the vulnerability, it may include occurrence's specific information. Optional. |
 | `vulnerabilities[].description`                      | A long text that describes the vulnerability. Optional. |
 | `vulnerabilities[].cve`                              | A fingerprint string value that represents a concrete occurrence of the vulnerability. It's used to determine whether two vulnerability occurrences are same or different. May not be 100% accurate. **This is NOT a [CVE](https://cve.mitre.org/)**. |
-| `vulnerabilities[].severity`                         | How much the vulnerability impacts the software. Possible values: `Undefined` (an analyzer has not provided this info), `Info`, `Unknown`, `Low`, `Medium`, `High`, `Critical`. |
-| `vulnerabilities[].confidence`                       | How reliable the vulnerability's assessment is. Possible values: `Undefined` (an analyzer has not provided this info), `Ignore`, `Unknown`, `Experimental`, `Low`, `Medium`, `High`, `Confirmed`. |
+| `vulnerabilities[].severity`                         | How much the vulnerability impacts the software. Possible values: `Undefined` (an analyzer has not provided this information), `Info`, `Unknown`, `Low`, `Medium`, `High`, `Critical`. |
+| `vulnerabilities[].confidence`                       | How reliable the vulnerability's assessment is. Possible values: `Undefined` (an analyzer has not provided this information), `Ignore`, `Unknown`, `Experimental`, `Low`, `Medium`, `High`, `Confirmed`. |
 | `vulnerabilities[].solution`                         | Explanation of how to fix the vulnerability. Optional. |
 | `vulnerabilities[].scanner`                          | A node that describes the analyzer used to find this vulnerability. |
 | `vulnerabilities[].scanner.id`                       | Id of the scanner as a snake_case string. |

doc/user/application_security/offline_deployments/index.md

@@ -73,7 +73,7 @@ hosted within your network.
 ## Specific scanner instructions
 
 Each individual scanner may be slightly different than the steps described
-above. You can find more info at each of the pages below:
+above. You can find more information at each of the pages below:
 
 - [Container scanning offline directions](../container_scanning/index.md#running-container-scanning-in-an-offline-environment)
 - [SAST offline directions](../sast/index.md#gitlab-sast-in-an-offline-environment)

doc/user/application_security/sast/index.md

@@ -443,8 +443,8 @@ the report JSON unless stated otherwise. Presence of optional fields depends on
 | `vulnerabilities[].message`             | A short text that describes the vulnerability, it may include the occurrence's specific information. Optional. |
 | `vulnerabilities[].description`         | A long text that describes the vulnerability. Optional. |
 | `vulnerabilities[].cve`                 | A fingerprint string value that represents a concrete occurrence of the vulnerability. Is used to determine whether two vulnerability occurrences are same or different. May not be 100% accurate. **This is NOT a [CVE](https://cve.mitre.org/)**. |
-| `vulnerabilities[].severity`            | How much the vulnerability impacts the software. Possible values: `Undefined` (an analyzer has not provided this info), `Info`, `Unknown`, `Low`, `Medium`, `High`, `Critical`. |
-| `vulnerabilities[].confidence`          | How reliable the vulnerability's assessment is. Possible values: `Undefined` (an analyzer has not provided this info), `Ignore`, `Unknown`, `Experimental`, `Low`, `Medium`, `High`, `Confirmed`. |
+| `vulnerabilities[].severity`            | How much the vulnerability impacts the software. Possible values: `Undefined` (an analyzer has not provided this information), `Info`, `Unknown`, `Low`, `Medium`, `High`, `Critical`. |
+| `vulnerabilities[].confidence`          | How reliable the vulnerability's assessment is. Possible values: `Undefined` (an analyzer has not provided this information), `Ignore`, `Unknown`, `Experimental`, `Low`, `Medium`, `High`, `Confirmed`. |
 | `vulnerabilities[].solution`            | Explanation of how to fix the vulnerability. Optional. |
 | `vulnerabilities[].scanner`             | A node that describes the analyzer used to find this vulnerability. |
 | `vulnerabilities[].scanner.id`          | Id of the scanner as a snake_case string. |

doc/user/group/index.md

@@ -99,7 +99,7 @@ To create a new Group, either:
 
 Add the following information:
 
-![new group info](img/create_new_group_info.png)
+![new group information](img/create_new_group_info.png)
 
 1. The **Group name** will automatically populate the URL. Optionally, you can change it.
    This is the name that displays in group views.

doc/user/index.md

@@ -100,7 +100,7 @@ directly from GitLab. No third-party integrations needed.
 There is a lot you can customize and configure
 to enjoy the best of GitLab.
 
-- [Settings](profile/index.md): Manage your user settings to change your personal info,
+- [Settings](profile/index.md): Manage your user settings to change your personal information,
   personal access tokens, authorized applications, etc.
 - [Authentication](../topics/authentication/index.md): Read through the authentication
   methods available in GitLab.

doc/user/packages/conan_repository/index.md

@@ -246,9 +246,9 @@ conan search Hello/0.1@my-group+my-project/beta --all --remote=gitlab
 
 The scope of your search will include all projects you have permission to access, this includes your private projects as well as all public projects.
 
-## Fetching Conan package info from the GitLab Package Registry
+## Fetching Conan package information from the GitLab Package Registry
 
-The `conan info` command will return info about a given package:
+The `conan info` command will return information about a given package:
 
 ```shell
 conan info Hello/0.1@my-group+my-project/beta
@@ -261,7 +261,7 @@ The GitLab Conan repository supports the following Conan CLI commands:
 - `conan upload`: Upload your recipe and package files to the GitLab Package Registry.
 - `conan install`: Install a conan package from the GitLab Package Registry, this includes using the `conanfile.txt` file.
 - `conan search`: Search the GitLab Package Registry for public packages, and private packages you have permission to view.
-- `conan info`: View the info on a given package from the GitLab Package Registry.
+- `conan info`: View the information on a given package from the GitLab Package Registry.
 - `conan remove`: Delete the package from the GitLab Package Registry.
 
 ## Using GitLab CI with Conan packages

doc/user/project/integrations/irker.md

@@ -4,7 +4,7 @@ GitLab provides a way to push update messages to an Irker server. When
 configured, pushes to a project will trigger the service to send data directly
 to the Irker server.
 
-See the project homepage for further info: <https://gitlab.com/esr/irker>
+See the project homepage for further information: <https://gitlab.com/esr/irker>
 
 ## Needed setup
 

doc/user/project/integrations/prometheus.md

@@ -775,7 +775,7 @@ GitLab unfurls the link as an embedded metrics panel:
 ![Embedded Metrics Rendered](img/embedded_metrics_rendered_v12_8.png)
 
 You can also embed a single chart. To get a link to a chart, click the
-**{ellipsis_v}** **More info** menu in the upper right corner of the chart,
+**{ellipsis_v}** **More actions** menu in the upper right corner of the chart,
 and select **Copy link to chart**, as shown in this example:
 
 ![Copy Link To Chart](img/copy_link_to_chart_v12_10.png)

doc/user/project/merge_requests/reviewing_and_managing_merge_requests.md

@@ -116,7 +116,7 @@ environment.
 Deployments that are ongoing will be shown, as well as the deploying/deployed state
 for environments. If it's the first time the branch is deployed, the link
 will return a `404` error until done. During the deployment, the stop button will
-be disabled. If the pipeline fails to deploy, the deployment info will be hidden.
+be disabled. If the pipeline fails to deploy, the deployment information will be hidden.
 
 ![Merge request pipeline](img/merge_request_pipeline.png)
 

doc/user/project/web_ide/index.md

@@ -270,7 +270,7 @@ terminal:
 - The `webide-file-sync` executable must start **after** the project
   directory is available. This is why we need to add `sleep 5` to the `command`.
   See [this issue](https://gitlab.com/gitlab-org/webide-file-sync/issues/7) for
-  more info.
+  more information.
 - `$CI_PROJECT_DIR` is a
   [predefined environment variable](../../../ci/variables/predefined_variables.md)
   for GitLab Runners. This is where your project's repository will be.