Add latest changes from gitlab-org/gitlab@15-1-stable-eev15.1.0-rc42

8 files changed, 51 insertions, 51 deletions

diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/dns_concepts.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/dns_concepts.md
index 5433e02b210..6daf671a751 100644
--- a/doc/user/project/pages/custom_domains_ssl_tls_certification/dns_concepts.md
+++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/dns_concepts.md
@@ -53,7 +53,7 @@ search the web for `how to add dns record on <my hosting service>`.
 
 ## `A` record
 
-A DNS A record maps a host to an IPv4 IP address.
+A DNS `A` record maps a host to an IPv4 IP address.
 It points a root domain as `example.com` to the host's IP address as
 `192.192.192.192`.
 
@@ -61,10 +61,10 @@ Example:
 
 - `example.com` => `A` => `192.192.192.192`
 
-## CNAME record
+## `CNAME` record
 
-CNAME records define an alias for canonical name for your server (one defined
-by an A record). It points a subdomain to another domain.
+`CNAME` records define an alias for canonical name for your server (one defined
+by an `A` record). It points a subdomain to another domain.
 
 Example:
 
@@ -84,14 +84,14 @@ Example:
 
 Then you can register emails for `users@mail.example.com`.
 
-## TXT record
+## `TXT` record
 
 A `TXT` record can associate arbitrary text with a host or other name. A common
 use is for site verification.
 
 Example:
 
-- `example.com`=> TXT => `"google-site-verification=6P08Ow5E-8Q0m6vQ7FMAqAYIDprkVV8fUf_7hZ4Qvc8"`
+- `example.com`=> `TXT` => `"google-site-verification=6P08Ow5E-8Q0m6vQ7FMAqAYIDprkVV8fUf_7hZ4Qvc8"`
 
 This way, you can verify the ownership for that domain name.
 
@@ -102,4 +102,4 @@ You can have one DNS record or more than one combined:
 - `example.com` => `A` => `192.192.192.192`
 - `www` => `CNAME` => `example.com`
 - `MX` => `mail.example.com`
-- `example.com`=> TXT => `"google-site-verification=6P08Ow5E-8Q0m6vQ7FMAqAYIDprkVV8fUf_7hZ4Qvc8"`
+- `example.com`=> `TXT` => `"google-site-verification=6P08Ow5E-8Q0m6vQ7FMAqAYIDprkVV8fUf_7hZ4Qvc8"`
diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md
index d970c0f9ef4..2c668e2c409 100644
--- a/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md
+++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md
@@ -47,13 +47,13 @@ this document for an [overview on DNS records](dns_concepts.md).
 
 #### 1. Add a custom domain to Pages
 
-Navigate to your project's **Setting > Pages** and click **+ New domain**
+Navigate to your project's **Setting > Pages** and select **+ New domain**
 to add your custom domain to GitLab Pages. You can choose whether to:
 
 - Add an [SSL/TLS certificate](#adding-an-ssltls-certificate-to-pages).
 - Leave it blank (it can be added later).
 
-Click **Create New Domain**.
+Select **Create New Domain**.
 
 ![Add new domain](img/add_certificate_to_pages.png)
 
@@ -82,20 +82,20 @@ Follow [this issue](https://gitlab.com/gitlab-org/gitlab/-/issues/214718) for de
 
 Root domains (`example.com`) require:
 
-- A [DNS A record](dns_concepts.md#a-record) pointing your domain to the Pages server.
-- A [TXT record](dns_concepts.md#txt-record) to verify your domain's ownership.
+- A [DNS `A` record](dns_concepts.md#a-record) pointing your domain to the Pages server.
+- A [`TXT` record](dns_concepts.md#txt-record) to verify your domain's ownership.
 
 | From                                          | DNS Record | To              |
 | --------------------------------------------- | ---------- | --------------- |
-| `example.com`                                 | A          | `35.185.44.232` |
-| `_gitlab-pages-verification-code.example.com` | `TXT`        | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
+| `example.com`                                 | `A`        | `35.185.44.232` |
+| `_gitlab-pages-verification-code.example.com` | `TXT`      | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
 
 For projects on GitLab.com, this IP is `35.185.44.232`.
 For projects living in other GitLab instances (CE or EE), please contact
 your sysadmin asking for this information (which IP address is Pages
 server running on your instance).
 
-![DNS A record pointing to GitLab.com Pages server](img/dns_add_new_a_record_example_updated_2018.png)
+![DNS `A` record pointing to GitLab.com Pages server](img/dns_add_new_a_record_example_updated_2018.png)
 
 WARNING:
 Note that if you use your root domain for your GitLab Pages website
@@ -111,7 +111,7 @@ as it most likely doesn't work if you set an [`MX` record](dns_concepts.md#mx-re
 Subdomains (`subdomain.example.com`) require:
 
 - A DNS [`ALIAS` or `CNAME` record](dns_concepts.md#cname-record) pointing your subdomain to the Pages server.
-- A DNS [TXT record](dns_concepts.md#txt-record) to verify your domain's ownership.
+- A DNS [`TXT` record](dns_concepts.md#txt-record) to verify your domain's ownership.
 
 | From                                                    | DNS Record      | To                    |
 |:--------------------------------------------------------|:----------------|:----------------------|
@@ -122,7 +122,7 @@ Note that, whether it's a user or a project website, the DNS record
 should point to your Pages domain (`namespace.gitlab.io`),
 without any `/project-name`.
 
-![DNS CNAME record pointing to GitLab.com project](img/dns_cname_record_example.png)
+![DNS `CNAME` record pointing to GitLab.com project](img/dns_cname_record_example.png)
 
 ##### For both root and subdomains
 
@@ -137,11 +137,11 @@ They require:
 
 | From                                              | DNS Record | To                     |
 | ------------------------------------------------- | ---------- | ---------------------- |
-| `example.com`                                     | A          | `35.185.44.232`        |
-| `_gitlab-pages-verification-code.example.com`     | `TXT`        | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
+| `example.com`                                     | `A`        | `35.185.44.232`        |
+| `_gitlab-pages-verification-code.example.com`     | `TXT`      | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
 |---------------------------------------------------+------------+------------------------|
-| `www.example.com`                                 | CNAME      | `namespace.gitlab.io`  |
-| `_gitlab-pages-verification-code.www.example.com` | `TXT`        | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
+| `www.example.com`                                 | `CNAME`    | `namespace.gitlab.io`  |
+| `_gitlab-pages-verification-code.www.example.com` | `TXT`      | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
 
 If you're using Cloudflare, check
 [Redirecting `www.domain.com` to `domain.com` with Cloudflare](#redirecting-wwwdomaincom-to-domaincom-with-cloudflare).
@@ -162,8 +162,8 @@ If you're using Cloudflare, check
 Once you have added all the DNS records:
 
 1. Go back at your project's **Settings > Pages**.
-1. Locate your domain name and click **Details**.
-1. Click the **Retry verification** button to activate your new domain.
+1. Locate your domain name and select **Details**.
+1. Select the **Retry verification** button to activate your new domain.
 
 ![Verify your domain](img/retry_domain_verification_v12_0.png)
 
@@ -208,15 +208,15 @@ For a root domain:
 
 | From                                              | DNS Record | To                     |
 | ------------------------------------------------- | ---------- | ---------------------- |
-| `example.com`                                     | `TXT`        | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
-| `_gitlab-pages-verification-code.example.com`     | `TXT`        | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
+| `example.com`                                     | `TXT`      | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
+| `_gitlab-pages-verification-code.example.com`     | `TXT`      | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
 
 For a subdomain:
 
 | From                                              | DNS Record | To                     |
 | ------------------------------------------------- | ---------- | ---------------------- |
-| `www.example.com`                                 | `TXT`        | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
-| `_gitlab-pages-verification-code.www.example.com` | `TXT`        | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
+| `www.example.com`                                 | `TXT`      | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
+| `_gitlab-pages-verification-code.www.example.com` | `TXT`      | `gitlab-pages-verification-code=00112233445566778899aabbccddeeff` |
 
 ### Adding more domain aliases
 
@@ -241,10 +241,10 @@ can use the following setup:
 1. In GitLab, verify your domain.
 1. In Cloudflare, create a DNS `CNAME` record pointing `www` to `domain.com`.
 1. In Cloudflare, add a Page Rule pointing `www.domain.com` to `domain.com`:
-   - Navigate to your domain's dashboard and click **Page Rules**
+   - Navigate to your domain's dashboard and select **Page Rules**
      on the top nav.
-   - Click **Create Page Rule**.
-   - Enter the domain `www.domain.com` and click **+ Add a Setting**.
+   - Select **Create Page Rule**.
+   - Enter the domain `www.domain.com` and select **+ Add a Setting**.
    - From the dropdown menu, choose **Forwarding URL**, then select the
      status code **301 - Permanent Redirect**.
    - Enter the destination URL `https://domain.com`.
@@ -285,7 +285,7 @@ meet these requirements.
 - To add the certificate at the time you add a new domain, go to your
   project's **Settings > Pages > New Domain**, add the domain name and the certificate.
 - To add the certificate to a domain previously added, go to your
-  project's **Settings > Pages**, locate your domain name, click **Details** and **Edit** to add the certificate.
+  project's **Settings > Pages**, locate your domain name, select **Details** and **Edit** to add the certificate.
 
 ![Pages project - adding certificates](img/add_certificate_to_pages.png)
 
diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
index cb22a200514..184e4f345c1 100644
--- a/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
+++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md
@@ -43,13 +43,13 @@ For **self-managed** GitLab instances, make sure your administrator has
 Once you've met the requirements, enable Let's Encrypt integration:
 
 1. Navigate to your project's **Settings > Pages**.
-1. Find your domain and click **Details**.
-1. Click **Edit** in the top-right corner.
+1. Find your domain and select **Details**.
+1. Select **Edit** in the top-right corner.
 1. Enable Let's Encrypt integration by switching **Automatic certificate management using Let's Encrypt**:
 
    ![Enable Let's Encrypt](img/lets_encrypt_integration_v12_1.png)
 
-1. Click **Save changes**.
+1. Select **Save changes**.
 
 Once enabled, GitLab obtains a LE certificate and add it to the
 associated Pages domain. GitLab also renews it automatically.
@@ -70,8 +70,8 @@ associated Pages domain. GitLab also renews it automatically.
 If you get an error **Something went wrong while obtaining the Let's Encrypt certificate**, first, make sure that your pages site is set to "Everyone" in your project's **Settings > General > Visibility**. This allows the Let's Encrypt Servers reach your pages site. Once this is confirmed, you can try obtaining the certificate again by following these steps:
 
 1. Go to your project's **Settings > Pages**.
-1. Click **Edit** on your domain.
-1. Click **Retry**.
+1. Select **Edit** on your domain.
+1. Select **Retry**.
 1. If you're still seeing the same error:
     1. Make sure you have properly set only one `CNAME` or `A` DNS record for your domain.
     1. Make sure your domain **doesn't have** an `AAAA` DNS record.
@@ -86,7 +86,7 @@ Another possible cause of this error is the `_redirects` file because the curren
 If you've enabled Let's Encrypt integration, but a certificate is absent after an hour and you see the message, "GitLab is obtaining a Let's Encrypt SSL certificate for this domain. This process can take some time. Please try again later.", try to remove and add the domain for GitLab Pages again by following these steps:
 
 1. Go to your project's **Settings > Pages**.
-1. Click **Remove** on your domain.
+1. Select **Remove** on your domain.
 1. [Add the domain again and verify it](index.md#1-add-a-custom-domain-to-pages).
 1. [Enable Let's Encrypt integration for your domain](#enabling-lets-encrypt-integration-for-your-custom-domain).
 1. If you still see the same message after some time:
diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/ssl_tls_concepts.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/ssl_tls_concepts.md
index 0c848a24dec..b080bee85aa 100644
--- a/doc/user/project/pages/custom_domains_ssl_tls_certification/ssl_tls_concepts.md
+++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/ssl_tls_concepts.md
@@ -23,7 +23,7 @@ highly recommendable.
 
 Let's start with an introduction to the importance of HTTPS.
 
-## Why should I care about HTTPS?
+## Why should you care about HTTPS?
 
 This might be your first question. If our sites are hosted by GitLab Pages,
 they are static, hence we are not dealing with server-side scripts
@@ -42,7 +42,7 @@ Now we have a different picture. [According to Josh Aas](https://letsencrypt.org
 > _We've since come to realize that HTTPS is important for almost all websites. It's important for any website that allows people to log in with a password, any website that [tracks its users](https://www.washingtonpost.com/news/the-switch/wp/2013/12/10/nsa-uses-google-cookies-to-pinpoint-targets-for-hacking/) in any way, any website that [doesn't want its content altered](https://arstechnica.com/tech-policy/2014/09/why-comcasts-javascript-ad-injections-threaten-security-net-neutrality/), and for any site that offers content people might not want others to know they are consuming. We've also learned that any site not secured by HTTPS [can be used to attack other sites](https://krebsonsecurity.com/2015/04/dont-be-fodder-for-chinas-great-cannon/)._
 
 Therefore, the reason why certificates are so important is that they encrypt
-the connection between the **client** (you, me, your visitors)
+the connection between the **client** (you, your visitors)
 and the **server** (where you site lives), through a keychain of
 authentications and validations.
 
diff --git a/doc/user/project/pages/getting_started/pages_new_project_template.md b/doc/user/project/pages/getting_started/pages_new_project_template.md
index b32d71a4887..92baba6b9c6 100644
--- a/doc/user/project/pages/getting_started/pages_new_project_template.md
+++ b/doc/user/project/pages/getting_started/pages_new_project_template.md
@@ -12,15 +12,15 @@ You can create a new project from a template and run the CI/CD pipeline to gener
 Use a template when you want to test GitLab Pages or start a new project that's already
 configured to generate a Pages site.
 
-1. From the top navigation, click the **+** button and select **New project**.
+1. From the top navigation, select the **+** button and select **New project**.
 1. Select **Create from Template**.
-1. Next to one of the templates starting with **Pages**, click **Use template**.
+1. Next to one of the templates starting with **Pages**, select **Use template**.
 
    ![Project templates for Pages](../img/pages_project_templates_v13_1.png)
 
-1. Complete the form and click **Create project**.
+1. Complete the form and select **Create project**.
 1. From the left sidebar, navigate to your project's **CI/CD > Pipelines**
-   and click **Run pipeline** to trigger GitLab CI/CD to build and deploy your
+   and select **Run pipeline** to trigger GitLab CI/CD to build and deploy your
    site.
 
 When the pipeline is finished, go to **Settings > Pages** to find the link to
diff --git a/doc/user/project/pages/introduction.md b/doc/user/project/pages/introduction.md
index 5846ceeb1b6..1ea7500273e 100644
--- a/doc/user/project/pages/introduction.md
+++ b/doc/user/project/pages/introduction.md
@@ -71,7 +71,7 @@ To restrict access to your website, enable [GitLab Pages Access Control](pages_a
 
 If you ever feel the need to purge your Pages content, you can do so by going
 to your project's settings through the gear icon in the top right, and then
-navigating to **Pages**. Click the **Remove pages** button to delete your Pages
+navigating to **Pages**. Select the **Remove pages** button to delete your Pages
 website.
 
 ![Remove pages](img/remove_pages.png)
@@ -259,20 +259,20 @@ for both the `/data` and `/data/` URL paths.
 
 ## Frequently Asked Questions
 
-### Can I download my generated pages?
+### Can you download your generated pages?
 
 Sure. All you need to do is download the artifacts archive from the job page.
 
-### Can I use GitLab Pages if my project is private?
+### Can you use GitLab Pages if your project is private?
 
 Yes. GitLab Pages doesn't care whether you set your project's visibility level
 to private, internal or public.
 
-### Can I create a personal or a group website
+### Can you create a personal or a group website?
 
 Yes. See the documentation about [GitLab Pages domain names, URLs, and base URLs](getting_started_part_one.md).
 
-### Do I need to create a user/group website before creating a project website?
+### Do you need to create a user/group website before creating a project website?
 
 No, you don't. You can create your project first and access it under
 `http(s)://namespace.example.io/projectname`.
diff --git a/doc/user/project/pages/pages_access_control.md b/doc/user/project/pages/pages_access_control.md
index 9b747e04973..eb897c176fa 100644
--- a/doc/user/project/pages/pages_access_control.md
+++ b/doc/user/project/pages/pages_access_control.md
@@ -10,9 +10,9 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 You can enable Pages access control on your project
 if your administrator has [enabled the access control feature](../../../administration/pages/index.md#access-control)
-on your GitLab instance. When enabled, only
+on your GitLab instance. When enabled, only authenticated
 [members of your project](../../permissions.md#project-members-permissions)
-(at least Guest) can access your website:
+(at least Guest) can access your website, by default:
 
 <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
 For a demonstration, see [Pages access controls](https://www.youtube.com/watch?v=tSPAr5mQYc8).
@@ -36,7 +36,7 @@ For a demonstration, see [Pages access controls](https://www.youtube.com/watch?v
      - **Only project members**: Only project members are able to browse the website.
      - **Everyone with access**: Everyone, both logged into and logged out of GitLab, is able to browse the website, no matter their project membership.
 
-1. Click **Save changes**. Note that your changes may not take effect immediately. GitLab Pages uses
+1. Select **Save changes**. Note that your changes may not take effect immediately. GitLab Pages uses
    a caching mechanism for efficiency. Your changes may not take effect until that cache is
    invalidated, which usually takes less than a minute.
 
diff --git a/doc/user/project/pages/redirects.md b/doc/user/project/pages/redirects.md
index 1db404f4888..791b6a1550a 100644
--- a/doc/user/project/pages/redirects.md
+++ b/doc/user/project/pages/redirects.md
@@ -164,7 +164,7 @@ Splats also match empty strings, so the previous rule redirects
 ### Rewrite all requests to a root `index.html`
 
 NOTE:
-If you are using [GitLab Pages integration with Let’s Encrypt](custom_domains_ssl_tls_certification/lets_encrypt_integration.md),
+If you are using [GitLab Pages integration with Let's Encrypt](custom_domains_ssl_tls_certification/lets_encrypt_integration.md),
 you must enable it before adding this rule. Otherwise, the redirection breaks the Let's Encrypt
 integration. For more details, see
 [GitLab Pages issue 649](https://gitlab.com/gitlab-org/gitlab-pages/-/issues/649).