Changes most instances of info to information

Some changes from "info" to "information" couldn't be made if
"info" appears in the UI.

Some instances of "info" remain in the GraphQL reference.

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).