Merge branch 'docs-aqualls-possessive-create' into 'master'

Clean up possessives in Create docset

See merge request gitlab-org/gitlab!50110

doc/administration/file_hooks.md

@@ -11,7 +11,7 @@ type: reference
 > - Until GitLab 12.8, the feature name was Plugins.
 
 With custom file hooks, GitLab administrators can introduce custom integrations
-without modifying GitLab's source code.
+without modifying the GitLab source code.
 
 NOTE:
 Instead of writing and supporting your own file hook you can make changes

doc/administration/gitaly/index.md

@@ -970,7 +970,7 @@ not an external process, there was very little overhead between:
 - GitLab application code that tried to look up data in Git repositories.
 - The Git implementation itself.
 
-Because the combination of Rugged and Unicorn was so efficient, GitLab's application code ended up with lots of
+Because the combination of Rugged and Unicorn was so efficient, the GitLab application code ended up with lots of
 duplicate Git object lookups. For example, looking up the `master` commit a dozen times in one
 request. We could write inefficient code without poor performance.
 
@@ -1006,7 +1006,7 @@ enables direct Git access.
 When GitLab calls a function that has a "Rugged patch", it performs two checks:
 
 - Is the feature flag for this patch set in the database? If so, the feature flag setting controls
-  GitLab's use of "Rugged patch" code.
+  the GitLab use of "Rugged patch" code.
 - If the feature flag is not set, GitLab tries accessing the filesystem underneath the
   Gitaly server directly. If it can, it uses the "Rugged patch":
   - If using Unicorn.

doc/administration/operations/moving_repositories.md

@@ -54,7 +54,7 @@ Each of the approaches we list can or does overwrite data in the target director
 
 ### Recommended approach in all cases
 
-GitLab's [backup and restore capability](../../raketasks/backup_restore.md) should be used. Git
+The GitLab [backup and restore capability](../../raketasks/backup_restore.md) should be used. Git
 repositories are accessed, managed, and stored on GitLab servers by Gitaly as a database. Data loss
 can result from directly accessing and copying Gitaly's files using tools like `rsync`.
 

doc/administration/repository_storage_paths.md

@@ -68,7 +68,7 @@ the example below, we add two more mount points that are named `nfs_1` and `nfs_
 respectively.
 
 NOTE:
-This example uses NFS. We do not recommend using EFS for storage as it may impact GitLab's performance. See the [relevant documentation](nfs.md#avoid-using-awss-elastic-file-system-efs) for more details.
+This example uses NFS. We do not recommend using EFS for storage as it may impact GitLab performance. See the [relevant documentation](nfs.md#avoid-using-awss-elastic-file-system-efs) for more details.
 
 **For installations from source**
 

doc/administration/server_hooks.md

@@ -160,7 +160,7 @@ them as they can change.
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5073) in GitLab 8.10.
 
-To have custom error messages appear in GitLab's UI when a commit is declined or an error occurs
+To have custom error messages appear in the GitLab UI when a commit is declined or an error occurs
 during the Git hook, your script should:
 
 - Send the custom error messages to either the script's `stdout` or `stderr`.
@@ -168,7 +168,7 @@ during the Git hook, your script should:
 
 ### Example custom error message
 
-This hook script written in Bash generates the following message in GitLab's UI:
+This hook script written in Bash generates the following message in the GitLab UI:
 
 ```shell
 #!/bin/sh

doc/development/code_intelligence/index.md

@@ -10,7 +10,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 This document describes the design behind [Code Intelligence](../../user/project/code_intelligence.md).
 
-GitLab's built-in Code Intelligence is powered by
+The built-in Code Intelligence in GitLab is powered by
 [LSIF](https://lsif.dev) and comes down to generating an LSIF document for a
 project in a CI job, processing the data, uploading it as a CI artifact and
 displaying this information for the files in the project.

doc/development/gitaly.md

@@ -13,7 +13,7 @@ Workhorse and GitLab Shell.
 ## Deep Dive
 
 In May 2019, Bob Van Landuyt hosted a Deep Dive (GitLab team members only: `https://gitlab.com/gitlab-org/create-stage/issues/1`)
-on GitLab's [Gitaly project](https://gitlab.com/gitlab-org/gitaly) and how to contribute to it as a
+on the [Gitaly project](https://gitlab.com/gitlab-org/gitaly) and how to contribute to it as a
 Ruby developer, to share his domain specific knowledge with anyone who may work in this part of the
 codebase in the future.
 

doc/development/lfs.md

@@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 ## Deep Dive
 
 In April 2019, Francisco Javier López hosted a Deep Dive (GitLab team members only: `https://gitlab.com/gitlab-org/create-stage/issues/1`)
-on GitLab's [Git LFS](../topics/git/lfs/index.md) implementation to share his domain
+on the GitLab [Git LFS](../topics/git/lfs/index.md) implementation to share his domain
 specific knowledge with anyone who may work in this part of the codebase in the future.
 You can find the [recording on YouTube](https://www.youtube.com/watch?v=Yyxwcksr0Qc),
 and the slides on [Google Slides](https://docs.google.com/presentation/d/1E-aw6-z0rYd0346YhIWE7E9A65zISL9iIMAOq2zaw9E/edit)

doc/gitlab-basics/README.md

@@ -46,4 +46,4 @@ These resources will help you get further acclimated to working on the command l
 - [Start using Git on the command line](start-using-git.md), for some simple Git commands.
 - [Command line basics](command-line-commands.md), to create and edit files using the command line.
 
-More Git resources are available in GitLab's [Git documentation](../topics/git/index.md).
+More Git resources are available in the GitLab [Git documentation](../topics/git/index.md).

doc/gitlab-basics/start-using-git.md

@@ -22,7 +22,7 @@ the command line and then push your changes to the remote server.
 
 This guide will help you get started with Git through the command line and can be your reference
 for Git commands in the future. If you're only looking for a quick reference of Git commands, you
-can download GitLab's [Git Cheat Sheet](https://about.gitlab.com/images/press/git-cheat-sheet.pdf).
+can download the GitLab [Git Cheat Sheet](https://about.gitlab.com/images/press/git-cheat-sheet.pdf).
 
 > For more information about the advantages of working with Git and GitLab:
 >
@@ -128,7 +128,7 @@ to our computer:
   - If you don't have 2FA enabled, use your account's password.
 
 NOTE:
-Authenticating via SSH is GitLab's recommended method. You can read more about credential storage
+Authenticating via SSH is the GitLab recommended method. You can read more about credential storage
 in the [Git Credentials documentation](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage).
 
 ## Git terminology

doc/integration/README.md

@@ -70,7 +70,7 @@ When trying to integrate GitLab with services that are using self-signed certifi
 There are two approaches you can take to solve this:
 
 1. Add the root certificate to the trusted chain of the OS.
-1. If using Omnibus, you can add the certificate to GitLab's trusted certificates.
+1. If using Omnibus, you can add the certificate to the GitLab trusted certificates.
 
 **OS main trusted chain**
 

doc/integration/external-issue-tracker.md

@@ -16,7 +16,7 @@ Once configured, you can reference external issues using the format `CODE-123`,
 
 These references in GitLab merge requests, commits, or comments are automatically converted to links to the issues.
 
-You can keep GitLab's issue tracker enabled in parallel or disable it. When enabled, the **Issues** link in the
+You can keep the GitLab issue tracker enabled in parallel or disable it. When enabled, the **Issues** link in the
 GitLab menu always opens the internal issue tracker. When disabled, the link is not visible in the menu.
 
 ## Configuration

doc/integration/jenkins.md

@@ -12,7 +12,7 @@ From GitLab, you can trigger a Jenkins build when you push code to a repository,
 request is created. In return, the Jenkins pipeline status is shown on merge requests widgets and
 on the GitLab project's home page.
 
-To better understand GitLab's Jenkins integration, watch the following video:
+To better understand the GitLab Jenkins integration, watch the following video:
 
 - [GitLab workflow with Jira issues and Jenkins pipelines](https://youtu.be/Jn-_fyra7xQ)
 
@@ -36,7 +36,7 @@ GitLab. Learn how to **migrate** from Jenkins to GitLab CI/CD in our
 
 ## Configure GitLab integration with Jenkins
 
-GitLab's Jenkins integration requires installation and configuration in both GitLab and Jenkins.
+The GitLab Jenkins integration requires installation and configuration in both GitLab and Jenkins.
 In GitLab, you need to grant Jenkins access to the relevant projects. In Jenkins, you need to
 install and configure several plugins.
 

doc/integration/oauth_provider.md

@@ -76,7 +76,7 @@ in the **Authorized applications** section under **Profile Settings > Applicatio
 
 ![Authorized_applications](img/oauth_provider_authorized_application.png)
 
-GitLab's OAuth applications support scopes, which allow various actions that any given
+The GitLab OAuth applications support scopes, which allow various actions that any given
 application can perform such as `read_user` and `api`. There are many more scopes
 available.
 

doc/integration/openid_connect_provider.md

@@ -22,7 +22,7 @@ mobile applications.
 On the client side, you can use [OmniAuth::OpenIDConnect](https://github.com/jjbohn/omniauth-openid-connect/) for Rails
 applications, or any of the other available [client implementations](https://openid.net/developers/libraries/#connect).
 
-GitLab's implementation uses the [doorkeeper-openid_connect](https://github.com/doorkeeper-gem/doorkeeper-openid_connect "Doorkeeper::OpenidConnect website") gem, refer
+The GitLab implementation uses the [doorkeeper-openid_connect](https://github.com/doorkeeper-gem/doorkeeper-openid_connect "Doorkeeper::OpenidConnect website") gem, refer
 to its README for more details about which parts of the specifications
 are supported.
 

doc/integration/shibboleth.md

@@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 NOTE:
 The preferred approach for integrating a Shibboleth authentication system
-with GitLab 10 or newer is to use [GitLab's SAML integration](saml.md). This documentation is for Omnibus GitLab 9.x installs or older.
+with GitLab 10 or newer is to use the [GitLab SAML integration](saml.md). This documentation is for Omnibus GitLab 9.x installs or older.
 
 In order to enable Shibboleth support in GitLab we need to use Apache instead of NGINX (It may be possible to use NGINX, however this is difficult to configure using the bundled NGINX provided in the Omnibus GitLab package). Apache uses mod_shib2 module for Shibboleth authentication and can pass attributes as headers to OmniAuth Shibboleth provider.
 

doc/integration/trello_power_up.md

@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Trello Power-Up
 
-GitLab's Trello Power-Up enables you to seamlessly attach
+The GitLab Trello Power-Up enables you to seamlessly attach
 GitLab **merge requests** to Trello cards.
 
 ![GitLab Trello PowerUp - Trello card](img/trello_card_with_gitlab_powerup.png)
@@ -35,7 +35,7 @@ If your instance's URL is `https://example.com`, your API URL is `https://exampl
 
 ## What is my Personal Access Token?
 
-Your GitLab's personal access token enables your GitLab account to be accessed
+Your GitLab personal access token enables your GitLab account to be accessed
 from Trello.
 
 > Find it in GitLab by clicking on your avatar (upright corner), from which you access

doc/topics/git/lfs/migrate_from_git_annex_to_git_lfs.md

@@ -32,7 +32,7 @@ ones that GitLab developed.
 - Git Annex requires a more complex setup, but has much more options than Git
   LFS. You can compare the commands each one offers by running `man git-annex`
   and `man git-lfs`.
-- Annex files cannot be browsed directly in GitLab's interface, whereas LFS
+- Annex files cannot be browsed directly in the GitLab interface, whereas LFS
   files can.
 
 ## Migration steps

doc/topics/git/numerous_undo_possibilities_in_git/index.md

@@ -8,7 +8,7 @@ type: howto
 # Numerous undo possibilities in Git
 
 In this tutorial, we will show you different ways of undoing your work in Git, for which
-we will assume you have a basic working knowledge of. Check GitLab's
+we will assume you have a basic working knowledge of. Check the GitLab
 [Git documentation](../index.md) for reference.
 
 Also, we will only provide some general information of the commands, which is enough

doc/topics/gitlab_flow.md

@@ -224,7 +224,7 @@ Not only does this rewrite history, but it also loses authorship information.
 Rebasing prevents the other authors from being attributed and sharing part of the [`git blame`](https://git-scm.com/docs/git-blame).
 
 If a merge involves many commits, it may seem more difficult to undo.
-You might consider solving this by squashing all the changes into one commit just before merging by using GitLab's [Squash-and-Merge](../user/project/merge_requests/squash_and_merge.md) feature.
+You might consider solving this by squashing all the changes into one commit just before merging by using the GitLab [Squash-and-Merge](../user/project/merge_requests/squash_and_merge.md) feature.
 Fortunately, there is an easy way to undo a merge with all its commits.
 The way to do this is by reverting the merge commit.
 Preserving this ability to revert a merge is a good reason to always use the "no fast-forward" (`--no-ff`) strategy when you merge manually.

doc/user/admin_area/settings/account_and_limit_settings.md

@@ -90,7 +90,7 @@ These settings can be found within:
   1. From the Group's homepage, navigate to **Settings > General**.
   1. Fill in the **Repository size limit (MB)** field in the **Naming, visibility** section.
   1. Click **Save changes**.
-- GitLab's global settings:
+- GitLab global settings:
   1. From the Dashboard, navigate to **Admin Area > Settings > General**.
   1. Expand the **Account and limit** section.
   1. Fill in the **Size limit per repository (MB)** field.

doc/user/admin_area/settings/visibility_and_access_controls.md

@@ -151,7 +151,7 @@ For more details, see [Exporting a project and its data](../../../user/project/s
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/4696) in GitLab 8.10.
 
-With GitLab's access restrictions, you can select with which protocols users can communicate with
+With GitLab access restrictions, you can select with which protocols users can communicate with
 GitLab.
 
 Disabling an access protocol does not block access to the server itself via those ports. The ports

doc/user/markdown.md

@@ -7,9 +7,9 @@ type: reference, howto
 
 # GitLab Markdown
 
-This Markdown guide is **valid only for GitLab's internal Markdown rendering system for entries and files**.
+This Markdown guide is **valid only for the GitLab internal Markdown rendering system for entries and files**.
 It is **not** valid for the [GitLab documentation website](https://docs.gitlab.com)
-or [GitLab's main website](https://about.gitlab.com), as they both use
+or the [GitLab main website](https://about.gitlab.com), as they both use
 [Kramdown](https://kramdown.gettalong.org) as their Markdown engine. The documentation
 website uses an extended Kramdown gem, [GitLab Kramdown](https://gitlab.com/gitlab-org/gitlab_kramdown).
 Consult the [GitLab Kramdown Guide](https://about.gitlab.com/handbook/markdown-guide/)
@@ -52,7 +52,7 @@ The documentation website had its [Markdown engine migrated from Redcarpet to Kr
 in October 2018.
 
 You may have older issues, merge requests, or Markdown documents in your
-repository that were written using some of the nuances of GitLab's RedCarpet version
+repository that were written using some of the nuances of the GitLab RedCarpet version
 of Markdown. Since CommonMark uses slightly stricter syntax, these documents
 might now appear a little differently since we have transitioned to CommonMark.
 
@@ -353,7 +353,7 @@ The wrapping tags can be either curly braces or square brackets:
 - [- deletion 4 -]
 ```
 
-![Inline diff as rendered by GitLab's interface](img/inline_diff_01_v13_3.png)
+![Inline diff as rendered by the GitLab interface](img/inline_diff_01_v13_3.png)
 
 ---
 
@@ -375,7 +375,7 @@ backslash `\`, otherwise the diff highlight don't render correctly:
 - {+ Text with escaped \`backticks\` inside +}
 ```
 
-![Inline diff with mixed formatting, as rendered by GitLab's interface](img/inline_diff_02_v13_3.png)
+![Inline diff with mixed formatting, as rendered by the GitLab interface](img/inline_diff_02_v13_3.png)
 
 ### Math
 
@@ -480,7 +480,7 @@ unordered or ordered lists:
    1. [x] Sub-task 2
 ```
 
-![A task list as rendered by GitLab's interface](img/completed_tasks_v13_3.png)
+![A task list as rendered by the GitLab interface](img/completed_tasks_v13_3.png)
 
 ### Table of contents
 

doc/user/project/index.md

@@ -50,7 +50,7 @@ When you create a project in GitLab, you'll have access to a large number of
   - [Merge Request Approvals](merge_requests/merge_request_approvals.md): Ask for approval before
   implementing a change **(STARTER)**
   - [Fix merge conflicts from the UI](merge_requests/resolve_conflicts.md):
-  Your Git diff tool right from GitLab's UI
+  Your Git diff tool right from the GitLab UI
   - [Review Apps](../../ci/review_apps/index.md): Live preview the results
   of the changes proposed in a merge request in a per-branch basis
 - [Labels](labels.md): Organize issues and merge requests by labels
@@ -69,7 +69,7 @@ When you create a project in GitLab, you'll have access to a large number of
 
 **GitLab CI/CD:**
 
-- [GitLab CI/CD](../../ci/README.md): GitLab's built-in [Continuous Integration, Delivery, and Deployment](https://about.gitlab.com/blog/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/) tool
+- [GitLab CI/CD](../../ci/README.md): the GitLab built-in [Continuous Integration, Delivery, and Deployment](https://about.gitlab.com/blog/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/) tool
   - [Container Registry](../packages/container_registry/index.md): Build and push Docker
   images out-of-the-box
   - [Auto Deploy](../../topics/autodevops/stages.md#auto-deploy): Configure GitLab CI/CD
@@ -100,7 +100,7 @@ When you create a project in GitLab, you'll have access to a large number of
 - [Insights](insights/index.md): configure the Insights that matter for your projects. **(ULTIMATE)**
 - [Security Dashboard](../application_security/security_dashboard/index.md): Security Dashboard. **(ULTIMATE)**
 - [Syntax highlighting](highlighting.md): an alternative to customize
-  your code blocks, overriding GitLab's default choice of language.
+  your code blocks, overriding the GitLab default choice of language.
 - [Badges](badges.md): badges for the project overview.
 - [Releases](releases/index.md): a way to track deliverables in your project as snapshot in time of
   the source, build output, other metadata, and other artifacts

doc/user/project/integrations/gitlab_slack_application.md

@@ -39,7 +39,7 @@ Keep in mind that you need to have the appropriate permissions for your Slack
 team in order to be able to install a new application, read more in Slack's
 docs on [Adding an app to your workspace](https://slack.com/help/articles/202035138-Add-an-app-to-your-workspace).
 
-To enable GitLab's service for your Slack team:
+To enable the GitLab service for your Slack team:
 
 1. Go to your project's **Settings > Integration > Slack application** (only
    visible on GitLab.com).

doc/user/project/integrations/jira.md

@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # GitLab Jira integration
 
-If you need to use Jira to track work that's implemented in GitLab, GitLab's Jira integrations make the process of working across systems more efficient.
+If you need to use Jira to track work that's implemented in GitLab, Jira integrations with GitLab make the process of working across systems more efficient.
 
 This page is about the GitLab Jira integration, which is available in every GitLab project by default, allowing you to connect it to any Jira instance, whether Cloud or self-managed. To compare features with the complementary Jira Development Panel integration, see [Jira integrations](jira_integrations.md).
 
@@ -18,7 +18,7 @@ Features include:
   - GitLab links to the Jira issue.
   - The Jira issue adds a comment with details and a link back to the activity in GitLab.
 - **Mention that a commit or MR resolves or closes a specific Jira issue** and when it's merged to the default branch:
-  - GitLab's MR displays a note that it closed the Jira issue. Prior to the merge, MRs indicate which issue they close.
+  - The GitLab MR displays a note that it closed the Jira issue. Prior to the merge, MRs indicate which issue they close.
   - The Jira issue shows the activity and is closed or otherwise transitioned as specified in your GitLab settings.
 - **View a list of Jira issues directly in GitLab** **(PREMIUM)**
 

doc/user/project/integrations/jira_integrations.md

@@ -11,7 +11,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 GitLab Issues are a tool for discussing ideas and planning and tracking work. However, your organization may already use Jira for these purposes, with
 extensive, established data and business processes they rely on.
 
-Although you can [migrate](../../../user/project/import/jira.md) your Jira issues and work exclusively in GitLab, you also have the option of continuing to use Jira by using GitLab's Jira integrations.
+Although you can [migrate](../../../user/project/import/jira.md) your Jira issues and work exclusively in GitLab, you also have the option of continuing to use Jira by using the GitLab Jira integrations.
 
 ## Integrations
 

doc/user/project/integrations/slack.md

@@ -110,7 +110,7 @@ result = Net::HTTP.get(URI('https://<GITLAB URL>'));0
 ```
 
 If GitLab is not trusting HTTPS connections to itself, then you may
-need to [add your certificate to GitLab's trusted certificates](https://docs.gitlab.com/omnibus/settings/ssl.html#install-custom-public-certificates).
+need to [add your certificate to the GitLab trusted certificates](https://docs.gitlab.com/omnibus/settings/ssl.html#install-custom-public-certificates).
 
 If GitLab is not trusting connections to Slack, then the GitLab
 OpenSSL trust store is incorrect. Some typical causes: overriding

doc/user/project/integrations/webhooks.md

@@ -1603,7 +1603,7 @@ Missing intermediate certificates are a common point of verification failure.
 
 ## Example webhook receiver
 
-If you want to see GitLab's webhooks in action for testing purposes you can use
+If you want to see GitLab webhooks in action for testing purposes you can use
 a simple echo script running in a console session. For the following script to
 work you need to have Ruby installed.
 

doc/user/project/issues/design_management.md

@@ -95,7 +95,7 @@ you can drag and drop designs onto the dedicated drop zone to upload them.
 
 [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/202634)
 in GitLab 12.10, you can also copy images from your file system and
-paste them directly on GitLab's Design page as a new design.
+paste them directly on the GitLab Design page as a new design.
 
 On macOS you can also take a screenshot and immediately copy it to
 the clipboard by simultaneously clicking <kbd>Control</kbd> + <kbd>Command</kbd> + <kbd>Shift</kbd> + <kbd>3</kbd>, and then paste it as a design.

doc/user/project/merge_requests/getting_started.md

@@ -126,7 +126,7 @@ Requesting a code review is an important part of contributing code. However, dec
 your code and asking for a review are no easy tasks. Using the "assignee" field for both authors and
 reviewers makes it hard for others to determine who's doing what on a merge request.
 
-GitLab's Merge Request Reviewers easily allow authors to request a review as well as see the status of the
+GitLab Merge Request Reviewers easily allow authors to request a review as well as see the status of the
 review. By selecting one or more users from the **Reviewers** field in the merge request's right-hand
 sidebar, the assigned reviewers will receive a notification of the request to review the merge request.
 

doc/user/project/merge_requests/reviewing_and_managing_merge_requests.md

@@ -232,7 +232,7 @@ you can preview the changes submitted to a feature-branch through a merge reques
 in a per-branch basis. No need to checkout the branch, install and preview locally;
 all your changes will be available to preview by anyone with the Review Apps link.
 
-With GitLab's [Route Maps](../../../ci/review_apps/index.md#route-maps) set, the
+With GitLab [Route Maps](../../../ci/review_apps/index.md#route-maps) set, the
 merge request widget takes you directly to the pages changed, making it easier and
 faster to preview proposed modifications.
 

doc/user/project/protected_branches.md

@@ -170,7 +170,7 @@ From time to time, it may be required to delete or clean up branches that are
 protected.
 
 User with [Maintainer permissions](../permissions.md) and up can manually delete protected
-branches via GitLab's web interface:
+branches via the GitLab web interface:
 
 1. Visit **Repository > Branches**
 1. Click on the delete icon next to the branch you wish to delete

doc/user/project/repository/index.md

@@ -48,7 +48,7 @@ to your repository's root.
 
 **From the user interface:**
 
-GitLab's UI allows you to perform lots of Git commands without having to
+The GitLab UI allows you to perform lots of Git commands without having to
 touch the command line. Even if you use the command line regularly, sometimes
 it's easier to do so [via GitLab UI](web_editor.md):
 
@@ -67,7 +67,7 @@ To get started with the command line, please read through the
 
 ### Find files
 
-Use GitLab's [file finder](file_finder.md) to search for files in a repository.
+Use the GitLab [file finder](file_finder.md) to search for files in a repository.
 
 ### Supported markup languages and extensions
 
@@ -141,7 +141,7 @@ their filenames include `openapi` or `swagger` and their extension is `yaml`,
 
 Then, to render them:
 
-1. Navigate to the OpenAPI file in your repository in GitLab's UI.
+1. Navigate to the OpenAPI file in your repository in the GitLab UI.
 1. Click the "Display OpenAPI" button which is located between the "Display source"
    and "Edit" buttons (when an OpenAPI file is found, it replaces the
    "Display rendered file" button).

doc/user/project/repository/reducing_the_repo_size_using_git.md

@@ -253,7 +253,7 @@ When using repository cleanup, note:
   are not be removed immediately. If you have access to the
   [Gitaly](../../../administration/gitaly/index.md) server, you may slip that delay and run `git gc --prune=now` to
   prune all loose objects immediately.
-- This process removes some copies of the rewritten commits from GitLab's cache and database,
+- This process removes some copies of the rewritten commits from the GitLab cache and database,
   but there are still numerous gaps in coverage and some of the copies may persist indefinitely.
   [Clearing the instance cache](../../../administration/raketasks/maintenance.md#clear-redis-cache)
   may help to remove some of them, but it should not be depended on for security purposes!

doc/user/project/repository/web_editor.md

@@ -94,7 +94,7 @@ the target branch. Click **Create directory** to finish.
 
 ## Create a new branch
 
-There are multiple ways to create a branch from GitLab's web interface.
+There are multiple ways to create a branch from the GitLab web interface.
 
 ### Create a new branch from an issue
 

doc/user/project/static_site_editor/index.md

@@ -169,7 +169,7 @@ title, layout template, or author, but can be used to pass any kind of metadata
 generator as the page renders out to HTML. Included at the very top of each data file, the
 front matter is often formatted as YAML or JSON and requires consistent and accurate syntax.
 
-To edit the front matter from the Static Site Editor you can use the GitLab's regular file editor,
+To edit the front matter from the Static Site Editor you can use the GitLab regular file editor,
 the Web IDE, or easily update the data directly from the WYSIWYG editor:
 
 1. Click the **Page settings** button on the bottom-right to reveal a web form with the data you

doc/user/project/wiki/index.md

@@ -64,7 +64,7 @@ When you're ready, click the **Create page** and the new page will be created.
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/33475) in GitLab 11.3.
 
-Starting with GitLab 11.3, any file that is uploaded to the wiki via GitLab's
+Starting with GitLab 11.3, any file that is uploaded to the wiki via the GitLab
 interface will be stored in the wiki Git repository, and it will be available
 if you clone the wiki repository locally. All uploaded files prior to GitLab
 11.3 are stored in GitLab itself. If you want them to be part of the wiki's Git