Merge branch 'docs-remove-log-out' into 'master'

Docs: Update pages to remove "log out"

See merge request gitlab-org/gitlab!44330

doc/administration/reply_by_email_postfix_setup.md

@@ -112,7 +112,7 @@ The instructions make the assumption that you will be using the email address `i
    q
    ```
 
-1. Log out of the `incoming` account and go back to being `root`:
+1. Sign out of the `incoming` account, and go back to being `root`:
 
    ```shell
    logout
@@ -164,7 +164,7 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
    try the above steps again, substituting `heirloom-mailx` for the `mail`
    command._
 
-1. Log out of the `incoming` account and go back to being `root`:
+1. Sign out of the `incoming` account, and go back to being `root`:
 
    ```shell
    logout
@@ -288,7 +288,7 @@ Courier, which we will install later to add IMAP authentication, requires mailbo
       q
       ```
 
-   1. Log out of the `incoming` account and go back to being `root`:
+   1. Sign out of the `incoming` account, and go back to being `root`:
 
       ```shell
       logout

doc/development/testing_guide/end_to_end/beginners_guide.md

@@ -196,8 +196,8 @@ end
 
 **What do we test?**
 
-1. Can we log in?
-1. Can we log out?
+1. Can we sign in?
+1. Can we sign out?
 
 **How do we test?**
 

doc/development/testing_guide/end_to_end/best_practices.md

@@ -241,7 +241,11 @@ All tests expect to be able to log in at the start of the test.
 
 For an example see: <https://gitlab.com/gitlab-org/gitlab/-/issues/34736>
 
-Ideally, any actions performed in an `after(:context)` (or [`before(:context)`](#limit-the-use-of-the-ui-in-beforecontext-and-after-hooks)) block would be performed via the API. But if it's necessary to do so via the UI (e.g., if API functionality doesn't exist), make sure to log out at the end of the block.
+Ideally, actions performed in an `after(:context)` (or
+[`before(:context)`](#limit-the-use-of-the-ui-in-beforecontext-and-after-hooks))
+block are performed using the API. If it's necessary to do so with the user
+interface (for example, if API functionality doesn't exist), be sure to sign
+out at the end of the block.
 
 ```ruby
 after(:all) do

doc/user/project/pages/pages_access_control.md

@@ -48,9 +48,10 @@ can access the website.
 
 ## Terminating a Pages session
 
-If you want to log out from your Pages website,
-you can do so by revoking application access token for GitLab Pages:
+To sign out of your GitLab Pages website, revoke the application access token
+for GitLab Pages:
 
-1. Navigate to your profile's **Settings > Applications**.
-1. Find **Authorized applications** at the bottom of the page.
-1. Find **GitLab Pages** and press the **Revoke** button.
+1. In the top menu, select your profile, and then select **Settings**.
+1. In the left sidebar, select **Applications**.
+1. Scroll to the **Authorized applications** section, find the **GitLab Pages**
+   entry, and select its **Revoke** button.