Merge branch 'docs-replace-product-names-ee' into 'master'

Docs: replace product names

See merge request gitlab-org/gitlab-ee!4365

doc/administration/audit_events.md

@@ -37,7 +37,7 @@ There are two kinds of events logged:
 
 ### Group events
 
-> Available in [GitLab Enterprise Edition Starter][ee].
+> Available in [GitLab Starter][ee].
 
 NOTE: **Note:**
 You need Owner [permissions] to view the group Audit Events page.
@@ -58,7 +58,7 @@ From there, you can see the following actions:
 
 ### Project events
 
-> Available in [GitLab Enterprise Edition Starter][ee].
+> Available in [GitLab Starter][ee].
 
 NOTE: **Note:**
 You need Master [permissions] or higher to view the project Audit Events page.
@@ -75,7 +75,7 @@ From there, you can see the following actions:
 
 ### Instance events
 
-> [Introduced][ee-2336] in [GitLab Enterprise Edition Premium][ee] 9.3.
+> [Introduced][ee-2336] in [GitLab Premium][ee] 9.3.
 Available only for GitLab administrators.
 
 Server-wide audit logging introduces the ability to observe user actions across
@@ -102,5 +102,5 @@ the filter drop-down. You can further filter by specific group, project or user
 ![audit log](audit_log.png)
 
 [ee-2336]: https://gitlab.com/gitlab-org/gitlab-ee/issues/2336
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [permissions]: ../user/permissions.md

doc/administration/auditor_users.md

 # Auditor users
 
->[Introduced][ee-998] in [GitLab Enterprise Edition Premium][eep] 8.17.
+>[Introduced][ee-998] in [GitLab Premium][eep] 8.17.
 
 Auditor users are given read-only access to all projects, groups, and other
 resources on the GitLab instance.
@@ -84,5 +84,5 @@ instance, with the following permissions/restrictions:
   - Cannot create project snippets
 
 [ee-998]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/998
-[eep]: https://about.gitlab.com/gitlab-ee/
+[eep]: https://about.gitlab.com/products/
 [permissions]: ../user/permissions.md

doc/administration/auth/README.md

@@ -9,7 +9,7 @@ providers.
 
 - [LDAP](ldap.md) Includes Active Directory, Apple Open Directory, Open LDAP,
   and 389 Server
-  - **(EES/EEP)** [LDAP for GitLab EE](ldap-ee.md): LDAP additions to GitLab Enterprise Editions
+  - **(Starter/Premium)** [LDAP for GitLab EE](ldap-ee.md): LDAP additions to GitLab Enterprise Editions
 - [OmniAuth](../../integration/omniauth.md) Sign in via Twitter, GitHub, GitLab.com, Google,
   Bitbucket, Facebook, Shibboleth, Crowd, Azure and Authentiq ID
 - [CAS](../../integration/cas.md) Configure GitLab to sign in using CAS

doc/administration/auth/how_to_configure_ldap_gitlab_ee/index.md

@@ -11,7 +11,7 @@ The present article follows [How to Configure LDAP with GitLab CE](../how_to_con
 
 ## GitLab Enterprise Edition - LDAP features
 
-[GitLab Enterprise Edition (EE)](https://about.gitlab.com/gitlab-ee/) has a number of advantages when it comes to integrating with Active Directory (LDAP):
+[GitLab Enterprise Edition (EE)](https://about.gitlab.com/products/) has a number of advantages when it comes to integrating with Active Directory (LDAP):
 
 - [Administrator Sync](#administrator-sync): As an extension of group sync, you can automatically manage your global GitLab administrators. Specify a group CN for `admin_group` and all members of the LDAP group will be given administrator privileges.
 - [Group Sync](#group-sync): This allows GitLab group membership to be automatically updated based on LDAP group members.

doc/administration/auth/ldap-ee.md

@@ -54,7 +54,7 @@ new groups they might be added to when the user logs in. That way they don't nee
 to wait for the hourly sync to be granted access to the groups that they are in
 in LDAP.
 
-In GitLab Enterprise Edition Premium, we can also add a GitLab group to sync with one or multiple LDAP groups or we can
+In GitLab Premium, we can also add a GitLab group to sync with one or multiple LDAP groups or we can
 also add a filter. The filter must comply with the syntax defined in [RFC 2254](https://tools.ietf.org/search/rfc2254).
 
 A group sync process will run every hour on the hour, and `group_base` must be set

doc/administration/database_load_balancing.md

 # Database Load Balancing
 
-> [Introduced][ee-1283] in [GitLab Enterprise Edition Premium][eep] 9.0.
+> [Introduced][ee-1283] in [GitLab Premium][eep] 9.0.
 
 Distribute read-only queries among multiple database servers.
 
@@ -158,7 +158,7 @@ log entries easier. For example:
 
 ## Handling Stale Reads
 
-> [Introduced][ee-3526] in [GitLab Enterprise Edition Premium][eep] 10.3.
+> [Introduced][ee-3526] in [GitLab Premium][eep] 10.3.
 
 To prevent reading from an outdated secondary the load balancer will check if it
 is in sync with the primary. If the data is determined to be recent enough the
@@ -192,7 +192,7 @@ production:
 
 [hot-standby]: https://www.postgresql.org/docs/9.6/static/hot-standby.html
 [ee-1283]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1283
-[eep]: https://about.gitlab.com/gitlab-ee/
+[eep]: https://about.gitlab.com/products/
 [reconfigure gitlab]: restart_gitlab.md#omnibus-gitlab-reconfigure "How to reconfigure Omnibus GitLab"
 [restart gitlab]: restart_gitlab.md#installations-from-source "How to restart GitLab"
 [wikipedia]: https://en.wikipedia.org/wiki/Load_balancing_(computing)

doc/administration/high_availability/consul.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-As part of its High Availability stack, GitLab EEP includes a bundled version of [Consul](http://consul.io) that can be managed through `/etc/gitlab/gitlab.rb`.
+As part of its High Availability stack, GitLab Premium includes a bundled version of [Consul](http://consul.io) that can be managed through `/etc/gitlab/gitlab.rb`.
 
 A Consul cluster consists of multiple server agents, as well as client agents that run on other nodes which need to talk to the consul cluster.
 

doc/administration/high_availability/database.md

@@ -6,8 +6,8 @@ PostgreSQL. This is the database that will be installed if you use the
 Omnibus package to manage your database.
 
 > Important notes:
-- This document will focus only on configuration supported with [GitLab Enterprise Edition Premium](https://about.gitlab.com/gitlab-ee/), using the Omnibus GitLab package.
-- If you are a Community Edition or Enterprise Edition Starter user, consider using a cloud hosted solution.
+- This document will focus only on configuration supported with [GitLab Premium](https://about.gitlab.com/products/), using the Omnibus GitLab package.
+- If you are a Community Edition or Starter user, consider using a cloud hosted solution.
 - This document will not cover installations from source.
 
 >

doc/administration/index.md

 # Administrator documentation
 
 Learn how to administer your GitLab instance (Community Edition and
-[Enterprise Editions](https://about.gitlab.com/gitlab-ee/)).
+[Enterprise Editions](https://about.gitlab.com/products/)).
 Regular users don't have access to GitLab administration tools and settings.
 
 GitLab.com is administered by GitLab, Inc., therefore, only GitLab team members have
@@ -15,13 +15,13 @@ Learn how to install, configure, update, and maintain your GitLab instance.
 ### Installing GitLab
 
 - [Install](../install/README.md): Requirements, directory structures, and installation methods.
-  - **(EES/EEP)** [Database load balancing](database_load_balancing.md): Distribute database queries among multiple database servers.
-  - **(EES/EEP)** [Omnibus support for external MySQL DB](https://docs.gitlab.com/omnibus/settings/database.html#using-a-mysql-database-management-server-enterprise-edition-only): Omnibus package supports configuring an external MySQL database.
-  - **(EES/EEP)** [Omnibus support for log forwarding](https://docs.gitlab.com/omnibus/settings/logs.html#udp-log-shipping-gitlab-enterprise-edition-only)
+  - **(Starter/Premium)** [Database load balancing](database_load_balancing.md): Distribute database queries among multiple database servers.
+  - **(Starter/Premium)** [Omnibus support for external MySQL DB](https://docs.gitlab.com/omnibus/settings/database.html#using-a-mysql-database-management-server-enterprise-edition-only): Omnibus package supports configuring an external MySQL database.
+  - **(Starter/Premium)** [Omnibus support for log forwarding](https://docs.gitlab.com/omnibus/settings/logs.html#udp-log-shipping-gitlab-enterprise-edition-only)
 - [High Availability](high_availability/README.md): Configure multiple servers for scaling or high availability.
   - [High Availability on AWS](../university/high-availability/aws/README.md): Set up GitLab HA on Amazon AWS.
-- **(EEP)** [GitLab Geo](../gitlab-geo/README.md): Replicate your GitLab instance to other geographical locations as a read-only fully operational version.
-- **(EEP)** [Pivotal Tile](../install/pivotal/index.md): Deploy GitLab as a pre-configured appliance using Ops Manager (BOSH) for Pivotal Cloud Foundry.
+- **(Premium)** [GitLab Geo](../gitlab-geo/README.md): Replicate your GitLab instance to other geographical locations as a read-only fully operational version.
+- **(Premium)** [Pivotal Tile](../install/pivotal/index.md): Deploy GitLab as a pre-configured appliance using Ops Manager (BOSH) for Pivotal Cloud Foundry.
 
 ### Configuring GitLab
 
@@ -34,7 +34,7 @@ Learn how to install, configure, update, and maintain your GitLab instance.
 - [GitLab Pages configuration for GitLab source installations](pages/source.md): Enable and configure GitLab Pages on
 [source installations](../install/installation.md#installation-from-source).
 - [Environment variables](environment_variables.md): Supported environment variables that can be used to override their defaults values in order to configure GitLab.
-- **(EES/EEP)** [Elasticsearch](../integration/elasticsearch.md): Enable Elasticsearch to empower GitLab's Advanced Global Search. Useful when you deal with a huge amount of data.
+- **(Starter/Premium)** [Elasticsearch](../integration/elasticsearch.md): Enable Elasticsearch to empower GitLab's Advanced Global Search. Useful when you deal with a huge amount of data.
 
 #### Customizing GitLab's appearance
 
@@ -75,15 +75,15 @@ created in snippets, wikis, and repos.
 - [Sign-up restrictions](../user/admin_area/settings/sign_up_restrictions.md): block email addresses of specific domains, or whitelist only specific domains.
 - [Access restrictions](../user/admin_area/settings/visibility_and_access_controls.md#enabled-git-access-protocols): Define which Git access protocols can be used to talk to GitLab (SSH, HTTP, HTTPS).
 - [Authentication/Authorization](../topics/authentication/index.md#gitlab-administrators): Enforce 2FA, configure external authentication with LDAP, SAML, CAS and additional Omniauth providers.
-  - **(EES/EEP)** [Sync LDAP](auth/ldap-ee.md)
-  - **(EES/EEP)** [Kerberos authentication](../integration/kerberos.md)
+  - **(Starter/Premium)** [Sync LDAP](auth/ldap-ee.md)
+  - **(Starter/Premium)** [Kerberos authentication](../integration/kerberos.md)
 - [Reply by email](reply_by_email.md): Allow users to comment on issues and merge requests by replying to notification emails.
   - [Postfix for Reply by email](reply_by_email_postfix_setup.md): Set up a basic Postfix mail
 server with IMAP authentication on Ubuntu, to be used with Reply by email.
-- **(EES/EEP)** [Email users](../tools/email.md): Email GitLab users from within GitLab.
+- **(Starter/Premium)** [Email users](../tools/email.md): Email GitLab users from within GitLab.
 - [User Cohorts](../user/admin_area/user_cohorts.md): Display the monthly cohorts of new users and their activities over time.
-- **(EES/EEP)** [Audit logs and events](audit_events.md): View the changes made within the GitLab server.
-- **(EEP)** [Auditor users](auditor_users.md): Users with read-only access to all projects, groups, and other resources on the GitLab instance.
+- **(Starter/Premium)** [Audit logs and events](audit_events.md): View the changes made within the GitLab server.
+- **(Premium)** [Auditor users](auditor_users.md): Users with read-only access to all projects, groups, and other resources on the GitLab instance.
 - [Reply by email](reply_by_email.md): Allow users to comment on issues and merge requests by replying to notification emails.
   - [Postfix for Reply by email](reply_by_email_postfix_setup.md): Set up a basic Postfix mail
 server with IMAP authentication on Ubuntu, to be used with Reply by email.
@@ -102,7 +102,7 @@ server with IMAP authentication on Ubuntu, to be used with Reply by email.
 - [Repository checks](repository_checks.md): Periodic Git repository checks.
 - [Repository storage paths](repository_storage_paths.md): Manage the paths used to store repositories.
 - [Repository storage rake tasks](raketasks/storage.md): A collection of rake tasks to list and migrate existing projects and attachments associated with it from Legacy storage to Hashed storage.
-- **(EES/EEP)** [Limit repository size](../user/admin_area/settings/account_and_limit_settings.md): Set a hard limit for your repositories' size.
+- **(Starter/Premium)** [Limit repository size](../user/admin_area/settings/account_and_limit_settings.md): Set a hard limit for your repositories' size.
 
 ## Continuous Integration settings
 

doc/administration/job_artifacts.md

@@ -88,13 +88,16 @@ _The artifacts are stored by default in
 ### Using object storage
 
 >**Notes:**
-- [Introduced][ee-1762] in [GitLab Enterprise Edition Premium][eep] 9.4.
+- [Introduced][ee-1762] in [GitLab Premium][eep] 9.4.
 - Since version 9.5, artifacts are [browsable], when object storage is enabled. 
   9.4 lacks this feature.
+> Available in [GitLab Premium](https://about.gitlab.com/products/) and
+[GitLab.com Silver](https://about.gitlab.com/gitlab-com/).
 
 If you don't want to use the local disk where GitLab is installed to store the
 artifacts, you can use an object storage like AWS S3 instead.
 This configuration relies on valid AWS credentials to be configured already.
+Use an [Object storage option][ee-os] like AWS S3 to store job artifacts.
 
 **In Omnibus installations:**
 
@@ -281,6 +284,7 @@ memory and disk I/O.
 [reconfigure gitlab]: restart_gitlab.md#omnibus-gitlab-reconfigure "How to reconfigure Omnibus GitLab"
 [restart gitlab]: restart_gitlab.md#installations-from-source "How to restart GitLab"
 [gitlab workhorse]: https://gitlab.com/gitlab-org/gitlab-workhorse "GitLab Workhorse repository"
-[eep]: https://about.gitlab.com/gitlab-ee/ "GitLab Enterprise Edition Premium"
+[eep]: https://about.gitlab.com/products/ "GitLab Premium"
 [ee-1762]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1762
 [browsable]: ../user/project/pipelines/job_artifacts.md#browsing-job-artifacts
+[ee-os]: https://docs.gitlab.com/ee/administration/job_artifacts.html#using-object-storage

doc/administration/operations/fast_ssh_key_lookup.md

 # Fast lookup of authorized SSH keys in the database
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/1631) in 
-> [GitLab Enterprise Edition Standard](https://about.gitlab.com/gitlab-ee) 9.3.
+> [GitLab Enterprise Edition Standard](https://about.gitlab.com/products) 9.3.
 >
 > [Available in](https://gitlab.com/gitlab-org/gitlab-ee/issues/3953) GitLab
 > Community Edition 10.4.

doc/administration/operations/index.md

@@ -13,6 +13,6 @@ by GitLab to another file system or another server.
 that to prioritize important jobs.
 - [Sidekiq MemoryKiller](sidekiq_memory_killer.md): Configure Sidekiq MemoryKiller
 to restart Sidekiq.
-- **(EES/EEP)** [Extra Sidekiq operations](extra_sidekiq_processes.md): Configure an extra set of Sidekiq processes to ensure certain queues always have dedicated workers, no matter the amount of jobs that need to be processed.
+- **(Starter/Premium)** [Extra Sidekiq operations](extra_sidekiq_processes.md): Configure an extra set of Sidekiq processes to ensure certain queues always have dedicated workers, no matter the amount of jobs that need to be processed.
 - [Unicorn](unicorn.md): Understand Unicorn and unicorn-worker-killer.
 - [Speed up SSH operations](fast_ssh_key_lookup.md): Authorize SSH users via a fast, indexed lookup to the GitLab database.

doc/administration/repository_storage_types.md

@@ -100,6 +100,6 @@ which is true for CI Cache and LFS Objects.
 | Pages           | Yes            | No             | -             | -              |
 | Docker Registry | Yes            | No             | -             | -              |
 | CI Build Logs   | No             | No             | -             | -              |
-| CI Artifacts    | No             | No             | Yes (EEP)     | -              |
+| CI Artifacts    | No             | No             | Yes (Premium) | -              |
 | CI Cache        | No             | No             | Yes           | -              |
-| LFS Objects     | Yes            | No             | Yes (EEP)     | -              |
+| LFS Objects     | Yes            | No             | Yes (Premium) | -              |

doc/api/README.md

@@ -30,7 +30,7 @@ following locations:
 - [Group Members](members.md)
 - [Issues](issues.md)
 - [Issue Boards](boards.md)
-- **(EEP)** [Group Issue Boards] (group_boards.md)
+- **(Premium)** [Group Issue Boards] (group_boards.md)
 - [Jobs](jobs.md)
 - [Keys](keys.md)
 - [Labels](labels.md)

doc/api/boards.md

@@ -141,7 +141,7 @@ Example response:
   }
 ```
 
-## Create a board (EES-Only)
+## Create a board (Starter-Only)
 
 Creates a board.
 
@@ -209,7 +209,7 @@ Example response:
   }
 ```
 
-## Delete a board (EES-Only)
+## Delete a board (Starter-Only)
 
 Deletes a board.
 

doc/api/epic_issues.md

@@ -4,7 +4,7 @@ Every API call to epic_issues must be authenticated.
 
 If a user is not a member of a group and the group is private, a `GET` request on that group will result to a `404` status code.
 
-Epics are available only in EEU. If epics feature is not available a `403` status code will be returned.
+Epics are available only in Ultimate. If epics feature is not available a `403` status code will be returned.
 
 ## List issues for an epic
 Gets all issues that are assigned to an epic and the authenticated user has  access to.

doc/api/epics.md

@@ -4,7 +4,7 @@ Every API call to epic must be authenticated.
 
 If a user is not a member of a group and the group is private, a `GET` request on that group will result to a `404` status code.
 
-Epics are available only in EEU. If epics feature is not available a `403` status code will be returned.
+Epics are available only in Ultimate. If epics feature is not available a `403` status code will be returned.
 
 ## Epic issues API
 

doc/api/jobs.md

@@ -297,7 +297,7 @@ Example of response
 > **Notes**:
 - [Introduced][ce-2893] in GitLab 8.5.
 - The use of `CI_JOB_TOKEN` in the artifacts download API was [introduced][ee-2346]
-  in [GitLab Enterprise Edition Premium][ee] 9.5.
+  in [GitLab Premium][ee] 9.5.
 
 Get job artifacts of a project.
 
@@ -345,7 +345,7 @@ Response:
 > **Notes**:
 - [Introduced][ce-5347] in GitLab 8.10.
 - The use of `CI_JOB_TOKEN` in the artifacts download API was [introduced][ee-2346]
-  in [GitLab Enterprise Edition Premium][ee] 9.5.
+  in [GitLab Premium][ee] 9.5.
 
 Download the artifacts archive from the given reference name and job provided the
 job finished successfully.
@@ -688,6 +688,6 @@ Example of response
 }
 ```
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [ee-2346]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2346
 [triggers]: ../ci/triggers/README.md#when-a-pipeline-depends-on-the-artifacts-of-another-pipeline

doc/api/projects.md

@@ -1335,7 +1335,7 @@ POST /projects/:id/housekeeping
 ## Push Rules
 
 >**Note:**
-Available in [GitLab Enterprise Edition Starter](https://about.gitlab.com/gitlab-ee).
+Available in [GitLab Starter](https://about.gitlab.com/products).
 
 ### Get project push rules
 
@@ -1430,7 +1430,7 @@ Read more in the [Project members](members.md) documentation.
 
 ## Start the pull mirroring process for a Project
 
-> Introduced in GitLab 10.3. **Note:** Available in [GitLab Enterprise Edition Starter](https://about.gitlab.com/gitlab-ee).
+> Introduced in GitLab 10.3. **Note:** Available in [GitLab Starter](https://about.gitlab.com/products).
 
 ```
 POST /projects/:id/mirror/pull

doc/ci/examples/README.md

@@ -43,7 +43,7 @@ There's also a collection of repositories with [example projects](https://gitlab
 
 ### Static Application Security Testing (SAST)
 
-- **(EEU)** [Scan your code for vulnerabilities](sast.md)
+- **(Ultimate)** [Scan your code for vulnerabilities](https://docs.gitlab.com/ee/ci/examples/sast.html)
 - [Scan your Docker images for vulnerabilities](sast_docker.md)
 
 ### Dynamic Application Security Testing (DAST)

doc/ci/examples/browser_performance.md

@@ -25,7 +25,7 @@ Once you set up the Runner, add a new job to `.gitlab-ci.yml`, called `performan
 
 This will create a `performance` job in your CI/CD pipeline and will run Sitespeed.io against the webpage you define. The GitLab plugin for Sitespeed.io downloaded in order to export the results to JSON. For further customization options of Sitespeed.io, including the ability to provide a list of URLs to test, please consult their [documentation](https://www.sitespeed.io/documentation/sitespeed.io/configuration/).
 
-For GitLab [Enterprise Edition Premium](https://about.gitlab.com/gitlab-ee/) users, this information can be automatically
+For [GitLab Premium](https://about.gitlab.com/products/) users, a performance score can be automatically
 extracted and shown right in the merge request widget. [Learn more on performance diffs in merge requests](../../user/project/merge_requests/browser_performance_testing.md).
 
 ## Performance testing on Review Apps

doc/ci/examples/code_climate.md

@@ -25,10 +25,10 @@ codequality:
 This will create a `codequality` job in your CI pipeline and will allow you to
 download and analyze the report artifact in JSON format.
 
-For GitLab [Enterprise Edition Starter][ee] users, this information can be automatically
+For [GitLab Starter][ee] users, this information can be automatically
 extracted and shown right in the merge request widget. [Learn more on code quality
 diffs in merge requests](../../user/project/merge_requests/code_quality_diff.md).
 
 [cli]: https://github.com/codeclimate/codeclimate
 [dind]: ../docker/using_docker_build.md#use-docker-in-docker-executor
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/ci/examples/dast.md

@@ -31,10 +31,10 @@ own) and finally write the results in the `gl-dast-report.json` file. You can
 then download and analyze the report artifact in JSON format.
 
 TIP: **Tip:**
-Starting with [GitLab Enterprise Edition Ultimate][ee] 10.4, this information will
+Starting with [GitLab Ultimate][ee] 10.4, this information will
 be automatically extracted and shown right in the merge request widget. To do
 so, the CI job must be named `dast` and the artifact path must be
 `gl-dast-report.json`.
 [Learn more about DAST results shown in merge requests](../../user/project/merge_requests/dast.md).
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/ci/examples/sast.md

 # Static Application Security Testing with GitLab CI/CD
 
 NOTE: **Note:**
-In order to use this tool, a [GitLab Enterprise Edition Ultimate][ee] license
+In order to use this tool, a [GitLab Ultimate][ee] license
 is needed.
 
 This example shows how to run
@@ -36,7 +36,7 @@ The results are sorted by the priority of the vulnerability:
 1. Everything else
 
 TIP: **Tip:**
-Starting with [GitLab Enterprise Edition Ultimate][ee] 10.3, this information will
+Starting with [GitLab Ultimate][ee] 10.3, this information will
 be automatically extracted and shown right in the merge request widget. To do
 so, the CI job must be named `sast` and the artifact path must be
 `gl-sast-report.json`.
@@ -53,4 +53,4 @@ The following languages and frameworks are supported.
 | Ruby          | [bundler-audit](https://github.com/rubysec/bundler-audit) |
 | Ruby on Rails | [brakeman](https://brakemanscanner.org) |
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/ci/examples/sast_docker.md

@@ -46,10 +46,10 @@ them in a [YAML file](https://github.com/arminc/clair-scanner/blob/master/README
 in our case its named `clair-whitelist.yml`.
 
 TIP: **Tip:**
-Starting with [GitLab Enterprise Edition Ultimate][ee] 10.4, this information will
+Starting with [GitLab Ultimate][ee] 10.4, this information will
 be automatically extracted and shown right in the merge request widget. To do
 so, the CI/CD job must be named `sast:container` and the artifact path must be
 `gl-sast-container-report.json`.
 [Learn more on application security testing results shown in merge requests](../../user/project/merge_requests/sast_docker.md).
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/ci/multi_project_pipeline_graphs.md

 # Multi-project pipeline graphs
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/2121) in
-[GitLab Enterprise Edition Premium 9.3](https://about.gitlab.com/2017/06/22/gitlab-9-3-released/#multi-project-pipeline-graphs).
+[GitLab Premium 9.3](https://about.gitlab.com/2017/06/22/gitlab-9-3-released/#multi-project-pipeline-graphs).
 
 When you set up [GitLab CI/CD](README.md) across multiple projects, you can visualize
 the entire pipeline, including all multi-project stages.

doc/ci/pipelines.md

@@ -191,7 +191,7 @@ by name. The order of severity is:
 With [multi-project pipeline graphs](multi_project_pipeline_graphs.md),
 you can visualize cross-project pipelines.
 
-It is available only in [GitLab Enterprise Edition Premium][eep].
+It is available only in [GitLab Premium][eep].
 
 ## How the pipeline duration is calculated
 
@@ -266,5 +266,5 @@ runners will not use regular runners, they must be tagged accordingly.
 [ce-7931]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7931
 [ce-9760]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9760
 [regexp]: https://gitlab.com/gitlab-org/gitlab-ce/blob/2f3dc314f42dbd79813e6251792853bc231e69dd/app/models/commit_status.rb#L99
-[eep]: https://about.gitlab.com/gitlab-ee/ "GitLab Enterprise Edition Premium"
+[eep]: https://about.gitlab.com/products/ "GitLab Premium"
 [ee-2121]: https://gitlab.com/gitlab-org/gitlab-ee/issues/2121

doc/ci/triggers/README.md

@@ -25,7 +25,7 @@ with the [GitLab Container Registry][registry]) in the following cases.
 
 > **Note**:
 The use of `CI_JOB_TOKEN` for multi-project pipelines was [introduced][ee-2017]
-in [GitLab Enterprise Edition Premium][ee] 9.3.
+in [GitLab Premium][ee] 9.3.
 
 This way of triggering can only be used when invoked inside `.gitlab-ci.yml`,
 and it creates a dependent pipeline relation visible on the
@@ -49,7 +49,7 @@ Read more about the [pipelines trigger API][trigapi].
 
 > **Note**:
 The use of `CI_JOB_TOKEN` in the artifacts download API was [introduced][ee-2346]
-in [GitLab Enterprise Edition Premium][ee] 9.5.
+in [GitLab Premium][ee] 9.5.
 
 With the introduction of dependencies between different projects, one of
 them may need to access artifacts created by a previous one. This process
@@ -276,7 +276,7 @@ removed with one of the future versions of GitLab. You are advised to
 [ee-2017]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2017
 [ee-2346]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2346
 [ci-229]: https://gitlab.com/gitlab-org/gitlab-ci/merge_requests/229
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [variables]: ../variables/README.md
 [predef]: ../variables/README.md#predefined-variables-environment-variables
 [registry]: ../../user/project/container_registry.md

doc/ci/variables/README.md

@@ -57,7 +57,7 @@ future GitLab releases.**
 | **CI_RUNNER_ID**                | 8.10   | 0.5    | The unique id of runner being used |
 | **CI_RUNNER_TAGS**              | 8.10   | 0.5    | The defined runner tags |
 | **CI_PIPELINE_ID**              | 8.10   | 0.5    | The unique id of the current pipeline that GitLab CI uses internally |
-| **CI_PIPELINE_SOURCE**          | 9.3    | all    | ([EEP]) The variable indicates how the pipeline was triggered, possible options are: push, web, trigger, schedule, api, pipeline |
+| **CI_PIPELINE_SOURCE**          | 9.3    | all    | ([Premium]) The variable indicates how the pipeline was triggered, possible options are: push, web, trigger, schedule, api, pipeline |
 | **CI_PIPELINE_TRIGGERED**       | all    | all    | The flag to indicate that job was [triggered] |
 | **CI_PIPELINE_SOURCE**          | 10.0   | all    | The source for this pipeline, one of: push, web, trigger, schedule, api, external. Pipelines created before 9.5 will have unknown as source |
 | **CI_PROJECT_DIR**              | all    | all    | The full path where the repository is cloned and where the job is run |
@@ -200,7 +200,7 @@ Once you set them, they will be available for all subsequent pipelines.
 ### Limiting environment scopes of secret variables
 
 >**Notes:**
-[Introduced][ee-2112] in [GitLab Enterprise Edition Premium][eep] 9.4.
+[Introduced][ee-2112] in [GitLab Premium][premium] 9.4.
 
 You can limit the environment scope of a secret variable by
 [defining which environments][envs] it can be available for.
@@ -467,7 +467,7 @@ export CI_REGISTRY_PASSWORD="longalfanumstring"
 
 [ee-2112]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2112
 [ce-13784]: https://gitlab.com/gitlab-org/gitlab-ce/issues/13784 "Simple protection of CI secret variables"
-[eep]: https://about.gitlab.com/gitlab-ee/ "Available only in GitLab Enterprise Edition Premium"
+[premium]: https://about.gitlab.com/products/ "Available only in GitLab Premium"
 [envs]: ../environments.md
 [protected branches]: ../../user/project/protected_branches.md
 [protected tags]: ../../user/project/protected_tags.md

doc/gitlab-geo/README.md

 # GitLab Geo
 
 > **Notes:**
-- GitLab Geo is part of [GitLab Enterprise Edition Premium][ee].
+- GitLab Geo is part of [GitLab Premium][ee].
 - Introduced in GitLab Enterprise Edition 8.9.
   We recommend you use it with at least GitLab Enterprise Edition 10.0 for
   basic Geo features, or latest version for a better experience.
@@ -40,7 +40,7 @@ Keep in mind that:
 
 - Secondaries talk to the primary to get user data for logins (API) and to
   replicate repositories, LFS Objects and Attachments (HTTPS + JWT).
-- Since GitLab Enterprise Edition Premium 10.0, the primary no longer talks to
+- Since GitLab Premium 10.0, the primary no longer talks to
   secondaries to notify for changes (API).
 
 ## Use-cases
@@ -234,6 +234,6 @@ Read the [GitLab Geo tuning](tuning.md) documentation.
 
 Read the [troubleshooting document](troubleshooting.md).
 
-[ee]: https://about.gitlab.com/gitlab-ee/ "GitLab Enterprise Edition landing page"
+[ee]: https://about.gitlab.com/products/ "GitLab Enterprise Edition landing page"
 [install-ee]: https://about.gitlab.com/downloads-ee/ "GitLab Enterprise Edition Omnibus packages downloads page"
 [install-ee-source]: https://docs.gitlab.com/ee/install/installation.html "GitLab Enterprise Edition installation from source"

doc/gitlab-geo/docker_registry.md

@@ -17,4 +17,4 @@ Docker Registry as well. For more information, read the
 when deploying the Registry, and how to setup the storage driver for GitLab's
 integrated [Container Registry](../administration/container_registry.md#container-registry-storage-driver).
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/install/README.md

@@ -37,7 +37,7 @@ the full process of installing GitLab on Google Container Engine (GKE), pushing
 - _Testing only!_ [DigitalOcean and Docker Machine](digitaloceandocker.md) -
   Quickly test any version of GitLab on DigitalOcean using Docker Machine.
 - [GitLab Pivotal Tile](pivotal/index.md) - Install and configure GitLab
-  Enterprise Edition Premium on Pivotal Cloud Foundry.
+  Premium on Pivotal Cloud Foundry.
 - [Getting started with GitLab and DigitalOcean](ttps://about.gitlab.com/2016/04/27/getting-started-with-gitlab-and-digitalocean/): requirements, installation process, updates.
 - [Demo: Cloud Native Development with GitLab](https://about.gitlab.com/2017/04/18/cloud-native-demo/): video demonstration on how to install GitLab on Kubernetes, build a project, create Review Apps, store Docker images in Container Registry, deploy to production on Kubernetes, and monitor with Prometheus.
 

doc/install/pivotal/index.md

 # GitLab Pivotal Tile
 
-> Introduced in [GitLab Enterprise Edition Premium][eep] 8.2.
+> Introduced in [GitLab Premium][eep] 8.2.
 
 Easily deploy GitLab as a pre-configured appliance using Ops Manager (BOSH) for
 [Pivotal Cloud Foundry][pcf].
@@ -21,7 +21,7 @@ and click a button to begin the upgrade process.
 
 ## Features
 
-The GitLab Pivotal Tile is based on [Enterprise Edition Premium] and includes nearly all of its features. The features in EEP but _not_ supported on the Tile are:
+The GitLab Pivotal Tile is based on [GitLab Premium] and includes nearly all of its features. The features in Premium but _not_ supported on the Tile are:
 
 * PostgreSQL
 * Pages
@@ -41,5 +41,5 @@ website:
 - [Product page](https://network.pivotal.io/products/p-gitlab/)
 - [Documentation](https://docs.pivotal.io/partners/gitlab/index.html)
 
-[eep]: https://about.gitlab.com/gitlab-ee/
+[premium]: https://about.gitlab.com/products/
 [pcf]: https://pivotal.io/platform

doc/integration/elasticsearch.md

 # Elasticsearch integration
 
 >
-[Introduced][ee-109] in GitLab [Enterprise Edition Starter][ee] 8.4. Support
+[Introduced][ee-109] in GitLab [Starter][ee] 8.4. Support
 for [Amazon Elasticsearch][aws-elastic] was [introduced][ee-1305] in GitLab
-[Enterprise Edition Starter][ee] 9.0.
+[Starter][ee] 9.0.
 
 This document describes how to set up Elasticsearch with GitLab. Once enabled,
 you'll have the benefit of fast search response times and the advantage of two
@@ -306,4 +306,4 @@ Here are some common pitfalls and how to overcome them:
 [install]: https://www.elastic.co/guide/en/elasticsearch/reference/current/_installation.html "Elasticsearch installation documentation"
 [pkg]: https://about.gitlab.com/downloads/ "Download Omnibus GitLab"
 [elastic-settings]: https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html#settings "Elasticsearch configuration settings"
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/integration/jira_development_panel.md

 # GitLab JIRA Development Panel integration
 
-> [Introduced][ee-2381] in [GitLab Enterprise Edition Premium][eep] 10.0.
+> [Introduced][ee-2381] in [GitLab Premium][eep] 10.0.
 
 As an extension to our [existing JIRA][existing-jira] project integration, you're now able to integrate
 all your GitLab projects with [JIRA Development Panel][jira-development-panel]. Both can be used
@@ -99,6 +99,6 @@ Click these links to see your GitLab repository data.
 
 [existing-jira]: ../user/project/integrations/jira.md
 [jira-development-panel]: https://confluence.atlassian.com/adminjiraserver070/integrating-with-development-tools-776637096.html#Integratingwithdevelopmenttools-Developmentpanelonissues
-[eep]: https://about.gitlab.com/gitlab-ee/
+[eep]: https://about.gitlab.com/products/
 [ee-2786]: https://gitlab.com/gitlab-org/gitlab-ee/issues/2786
 [relative-url]: https://docs.gitlab.com/omnibus/settings/configuration.html#configuring-a-relative-url-for-gitlab

doc/integration/kerberos.md

 # Kerberos integration
 
 >**Note:**
-Available in [GitLab Enterprise Edition Starter][ee].
+Available in [GitLab Starter][ee].
 
 GitLab can integrate with [Kerberos][kerb] as an authentication mechanism.
 
@@ -316,4 +316,4 @@ See also: [Git v2.11 release notes](https://github.com/git/git/blob/master/Docum
 [kerb]: https://web.mit.edu/kerberos/
 [mit]: http://web.mit.edu/
 [why-kerb]: http://web.mit.edu/sipb/doc/working/guide/guide/node20.html
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/push_rules/push_rules.md

@@ -61,23 +61,23 @@ The following options are available.
 
 | Push rule | GitLab version | Description |
 | --------- | :------------: | ----------- |
-| Removal of tags with `git push` | **EES** 7.10 | Forbid users to remove git tags with `git push`. Tags will still be able to be deleted through the web UI. |
-| Check whether author is a GitLab user | **EES** 7.10 | Restrict commits by author (email) to existing GitLab users. |
-| Check whether committer is the current authenticated user | **EEP** 10.2 | GitLab will reject any commit that was not committed by the current authenticated user |
-| Check whether commit is signed through GPG | **EEP** 10.1 | Reject commit when it is not signed through GPG. Read [signing commits with GPG][signing-commits]. |
-| Prevent committing secrets to Git | **EES** 8.12 | GitLab will reject any files that are likely to contain secrets. Read [what files are forbidden](#prevent-pushing-secrets-to-the-repository). |
-| Restrict by commit message | **EES** 7.10 | Only commit messages that match this Ruby regular expression are allowed to be pushed. Leave empty to allow any commit message. |
-| Restrict by branch name | **EES** 9.3 | Only branch names that match this Ruby regular expression are allowed to be pushed. Leave empty to allow any branch name. |
-| Restrict by commit author's email | **EES** 7.10 | Only commit author's email that match this Ruby regular expression are allowed to be pushed. Leave empty to allow any email. |
-| Prohibited file names | **EES** 7.10 | Any committed filenames that match this Ruby regular expression are not allowed to be pushed. Leave empty to allow any filenames. |
-| Maximum file size | **EES** 7.12 | Pushes that contain added or updated files that exceed this file size (in MB) are rejected. Set to 0 to allow files of any size. |
+| Removal of tags with `git push` | **Starter** 7.10 | Forbid users to remove git tags with `git push`. Tags will still be able to be deleted through the web UI. |
+| Check whether author is a GitLab user | **Starter** 7.10 | Restrict commits by author (email) to existing GitLab users. |
+| Check whether committer is the current authenticated user | **Premium** 10.2 | GitLab will reject any commit that was not committed by the current authenticated user |
+| Check whether commit is signed through GPG | **Premium** 10.1 | Reject commit when it is not signed through GPG. Read [signing commits with GPG][signing-commits]. |
+| Prevent committing secrets to Git | **Starter** 8.12 | GitLab will reject any files that are likely to contain secrets. Read [what files are forbidden](#prevent-pushing-secrets-to-the-repository). |
+| Restrict by commit message | **Starter** 7.10 | Only commit messages that match this Ruby regular expression are allowed to be pushed. Leave empty to allow any commit message. |
+| Restrict by branch name | **Starter** 9.3 | Only branch names that match this Ruby regular expression are allowed to be pushed. Leave empty to allow any branch name. |
+| Restrict by commit author's email | **Starter** 7.10 | Only commit author's email that match this Ruby regular expression are allowed to be pushed. Leave empty to allow any email. |
+| Prohibited file names | **Starter** 7.10 | Any committed filenames that match this Ruby regular expression are not allowed to be pushed. Leave empty to allow any filenames. |
+| Maximum file size | **Starter** 7.12 | Pushes that contain added or updated files that exceed this file size (in MB) are rejected. Set to 0 to allow files of any size. |
 
 >**Tip:**
 You can check your regular expressions at <http://rubular.com>.
 
 ## Prevent pushing secrets to the repository
 
-> [Introduced][ee-385] in [GitLab Enterprise Edition Starter][ee] 8.12.
+> [Introduced][ee-385] in [GitLab Starter][ee] 8.12.
 
 You can turn on a predefined blacklist of files which won't be allowed to be
 pushed to a repository.
@@ -154,4 +154,4 @@ bash_history
 [ee-385]: https://gitlab.com/gitlab-org/gitlab-ee/issues/385
 [list]: https://gitlab.com/gitlab-org/gitlab-ee/blob/master/lib/gitlab/checks/files_blacklist.yml
 [hooks]: https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/tools/email.md

 # Email from GitLab
 
 >**Note:**
-Available in [GitLab Enterprise Edition Starter][ee].
+Available in [GitLab Starter][ee].
 
 As a GitLab administrator you can email GitLab users from within GitLab.
 
@@ -38,4 +38,4 @@ to keep the simplicity of this feature.
 On unsubscribe, user will receive an email notifying that unsubscribe happened.
 The endpoint that provides the unsubscribe option is rate-limited.
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/topics/autodevops/index.md

@@ -198,13 +198,13 @@ static analysis and other code checks on the current code. The report is
 created, and is uploaded as an artifact which you can later download and check
 out.
 
-In GitLab Enterprise Edition Starter, differences between the source and
+In GitLab Starter, differences between the source and
 target branches are also
 [shown in the merge request widget](../../user/project/merge_requests/code_quality_diff.md).
 
 ### Auto SAST
 
-> Introduced in [GitLab Enterprise Edition Ultimate][ee] 10.3.
+> Introduced in [GitLab Ultimate][ee] 10.3.
 
 Static Application Security Testing (SAST) uses the
 [gl-sast Docker image](https://gitlab.com/gitlab-org/gl-sast) to run static
@@ -212,7 +212,7 @@ analysis on the current code and checks for potential security issues. Once the
 report is created, it's uploaded as an artifact which you can later download and
 check out.
 
-In GitLab Enterprise Edition Ultimate, any security warnings are also
+In GitLab Ultimate, any security warnings are also
 [shown in the merge request widget](../../user/project/merge_requests/sast.md).
 
 ### Auto SAST for Docker images
@@ -225,7 +225,7 @@ Docker image and checks for potential security issues. Once the report is
 created, it's uploaded as an artifact which you can later download and
 check out.
 
-In GitLab Enterprise Edition Ultimate, any security warnings are also
+In GitLab Ultimate, any security warnings are also
 [shown in the merge request widget](../../user/project/merge_requests/sast_docker.md).
 
 ### Auto Review Apps
@@ -256,7 +256,7 @@ be deleted.
 
 ### Auto DAST
 
-> Introduced in [GitLab Enterprise Edition Ultimate][ee] 10.4.
+> Introduced in [GitLab Ultimate][ee] 10.4.
 
 Dynamic Application Security Testing (DAST) uses the
 popular open source tool [OWASP ZAProxy](https://github.com/zaproxy/zaproxy)
@@ -264,12 +264,12 @@ to perform an analysis on the current code and checks for potential security
 issues. Once the report is created, it's uploaded as an artifact which you can
 later download and check out.
 
-In GitLab Enterprise Edition Ultimate, any security warnings are also
+In GitLab Ultimate, any security warnings are also
 [shown in the merge request widget](../../user/project/merge_requests/dast.md).
 
 ### Auto Browser Performance Testing
 
-> Introduced in [GitLab Enterprise Edition Premium][ee] 10.4.
+> Introduced in [GitLab Premium][ee] 10.4.
 
 Auto Browser Performance Testing utilizes the [Sitespeed.io container](https://hub.docker.com/r/sitespeedio/sitespeed.io/) to measure the performance of a web page. A JSON report is created and uploaded as an artifact, which includes the overall performance score for each page. By default, the root page of Review and Production environments will be tested. If you would like to add additional URL's to test, simply add the paths to a file named `.gitlab-urls.txt` in the root directory, one per line. For example:
 
@@ -279,7 +279,7 @@ Auto Browser Performance Testing utilizes the [Sitespeed.io container](https://h
 /direction
 ```
 
-In GitLab Enterprise Edition Premium, performance differences between the source
+In GitLab Premium, performance differences between the source
 and target branches are [shown in the merge request widget](../../user/project/merge_requests/browser_performance_testing.md).
 
 ### Auto Deploy
@@ -594,4 +594,4 @@ curl --data "value=true" --header "PRIVATE-TOKEN: personal_access_token" https:/
 [postgresql]: https://www.postgresql.org/
 [Auto DevOps template]: https://gitlab.com/gitlab-org/gitlab-ci-yml/blob/master/Auto-DevOps.gitlab-ci.yml
 [GitLab Omnibus Helm Chart]: ../../install/kubernetes/gitlab_omnibus.md
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/user/group/contribution_analytics/index.md

 # Contribution Analytics
 
 >**Note:**
-This feature was introduced in [GitLab Enterprise Edition Starter][ee] 8.3.
+This feature was introduced in [GitLab Starter][ee] 8.3.
 
 Track your team members' activity across your organization.
 
@@ -54,4 +54,4 @@ which are depicted in a table that can be sorted by:
 
 ![Contribution analytics contributions table](img/group_stats_table.png)
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/user/group/epics/index.md

 # Epics
 
-> Introduced in [GitLab Enterprise Edition Ultimate][ee] 10.2.
+> Introduced in [GitLab Ultimate][ee] 10.2.
 
 Epics let you manage your portfolio of projects more efficiently and with less
 effort by tracking groups of issues that share a theme, across projects and
@@ -71,5 +71,5 @@ then you already have access to its projects' issues.
 
 You may also consult the [group permissions table][permissions].
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [permissions]: ../../permissions.md#group-members-permissions

doc/user/group/index.md

@@ -152,7 +152,10 @@ There are two different ways to add a new project to a group:
 
     ![Select group](img/select_group_dropdown.png)
 
-### (EEP) Default project creation level
+### Default project creation level
+
+> Available in [GitLab Premium](https://about.gitlab.com/products/) and
+[GitLab.com Silver](https://about.gitlab.com/gitlab-com/).
 
 This feature allows groups to define a default project creation level.
 
@@ -161,8 +164,6 @@ this can be changed within the group settings for a group, or the default settin
 changed within the Admin area (`Settings`, `Visibility and Access Controls`). This
 can be `None`, `Masters`, or `Developers + Masters`.
 
-It is available only in [GitLab Enterprise Edition Premium][eep].
-
 ## Transfer projects into groups
 
 Learn how to [transfer a project into a group](../project/index.md#transfer-an-existing-project-into-a-group).
@@ -181,7 +182,7 @@ See [the GitLab Enterprise Edition documentation](../../integration/ldap.md) for
 
 ## Epics
 
-> Introduced in [GitLab Enterprise Edition Ultimate][ee] 10.2.
+> Introduced in [GitLab Ultimate][ee] 10.2.
 
 Epics let you manage your portfolio of projects more efficiently and with less
 effort by tracking groups of issues that share a theme, across projects and
@@ -266,14 +267,17 @@ To enable this feature, navigate to the group settings page. Select
 
 ![Checkbox for share with group lock](img/share_with_group_lock.png)
 
-#### Member Lock (EES/EEP)
+#### Member Lock
 
-Available in [GitLab Enterprise Edition Starter](https://about.gitlab.com/gitlab-ee/),
-with **Member Lock** it is possible to lock membership in project to the
+> Available in [GitLab Starter](https://about.gitlab.com/products/) and
+[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
+
+With **Member Lock** it is possible to lock membership in project to the
 level of members in group.
 
 Member Lock lets a group owner to lock down any new project membership to all the
 projects within the group, allowing tighter control over project membership.
+Learn more about [Member Lock](https://docs.gitlab.com/ee/user/group/index.html#member-lock).
 
 For instance, if you want to lock the group for an [Audit Event](../../administration/audit_events.md),
 you enable Member Lock to guarantee that any membership is added or changed
@@ -294,17 +298,19 @@ request to add new user to project through API will not be possible.
 access each project's settings, and remove any project from the same screen.
 - **Webhooks**: configure [webhooks](../project/integrations/webhooks.md)
 and [push rules](../../push_rules/push_rules.md) to your group
-(Push Rules is available in [GitLab Enteprise Edition Starter][ee].)
+(Push Rules is available in [GitLab Starter][ee].)
 - **Audit Events**: view [Audit Events](../../administration/audit_events.md)
-for the group (GitLab admins only, available in [GitLab Enterprise Edition Starter][ee])
+for the group (GitLab admins only, available in [GitLab Starter][ee])
 - **Pipelines quota**: keep track of the
 [pipeline quota](../admin_area/settings/continuous_integration.md) for the group
 
-## User contribution analysis (EES/EEP)
+## User contribution analysis
+
+> Available in [GitLab Starter](https://about.gitlab.com/products/) and
+[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
 
 With [GitLab Contribution Analytics](contribution_analytics/index.md)
 you have an overview of the contributions (pushes, merge requests,
 and issues) performed my your group members.
 
 [ee]: https://about.gitlab.com/products/
-[eep]: https://about.gitlab.com/gitlab-ee/ "GitLab Enterprise Edition Premium"

doc/user/permissions.md

@@ -121,14 +121,16 @@ and drag issues around. Read though the
 [documentation on Issue Boards permissions](project/issue_board.md#permissions)
 to learn more.
 
-### File Locking permissions (EEP)
+### File Locking permissions
+
+> Available in [GitLab Premium](https://about.gitlab.com/products/) and [GitLab.com Silver](https://about.gitlab.com/gitlab-com/).
 
 The user that locks a file or directory is the only one that can edit and push their changes back to the repository where the locked objects are located.
 
 Read through the documentation on [permissions for File Locking](https://docs.gitlab.com/ee/user/project/file_lock.html#permissions-on-file-locking) to learn more.
 
 File Locking is available in
-[GitLab Enterprise Edition Premium](https://about.gitlab.com/gitlab-ee/) only.
+[GitLab Premium](https://about.gitlab.com/products/) only.
 
 ### Confidential Issues permissions
 
@@ -194,7 +196,7 @@ by an administrator under **Admin > Application Settings**.
 
 ## Auditor users
 
->[Introduced][ee-998] in [GitLab Enterprise Edition Premium][eep] 8.17.
+>[Introduced][ee-998] in [GitLab Premium][eep] 8.17.
 
 Auditor users are given read-only access to all projects, groups, and other
 resources on the GitLab instance.
@@ -279,12 +281,14 @@ for details about the pipelines security model.
 Since GitLab 8.15, LDAP user permissions can now be manually overridden by an admin user.
 Read through the documentation on [LDAP users permissions](../administration/auth/how_to_configure_ldap_gitlab_ee/index.md) to learn more.
 
-## Auditor users permissions (EEP)
+## Auditor users permissions
+
+> Available in [GitLab Premium](https://about.gitlab.com/products/).
 
 An Auditor user should be able to access all projects and groups of a GitLab instance
 with the permissions described on the documentation on [auditor users permissions](https://docs.gitlab.com/ee/administration/auditor_users.html#permissions-and-restrictions-of-an-auditor-user).
 
-Auditor users are available in [GitLab Enterprise Edition Premium](https://about.gitlab.com/gitlab-ee/)
+Auditor users are available in [GitLab Premium](https://about.gitlab.com/products/)
 only.
 
 [^1]: On public and internal projects, all users are able to perform this action
@@ -298,4 +302,4 @@ only.
 [ce-18994]: https://gitlab.com/gitlab-org/gitlab-ce/issues/18994
 [new-mod]: project/new_ci_build_permissions_model.md
 [ee-998]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/998
-[eep]: https://about.gitlab.com/gitlab-ee/
+[eep]: https://about.gitlab.com/products/

doc/user/project/canary_deployments.md

 # Canary Deployments
 
-> [Introduced][ee-1659] in [GitLab Enterprise Edition Premium][eep] 9.1.
+> [Introduced][ee-1659] in [GitLab Premium][eep] 9.1.
 
 A popular [Continuous Integration](https://en.wikipedia.org/wiki/Continuous_integration)
 strategy, where a small portion of the fleet is updated to the new version of
@@ -63,7 +63,7 @@ can easily notice them.
 ![Canary deployments on Deploy Board](img/deploy_boards_canary_deployments.png)
 
 [autodeploy]: ../../ci/autodeploy/index.md "GitLab Autodeploy"
-[eep]: https://about.gitlab.com/gitlab-ee/
+[eep]: https://about.gitlab.com/products/
 [ee-1659]: https://gitlab.com/gitlab-org/gitlab-ee/issues/1659
 [kube-canary]: https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments
 [deploy board]: deploy_boards.md

doc/user/project/clusters/index.md

@@ -190,9 +190,9 @@ The result will then be:
 
 ## Multiple Kubernetes clusters
 
-> Introduced in [GitLab Enterprise Edition Premium][ee] 10.3.
+> Introduced in [GitLab Premium][ee] 10.3.
 
-With GitLab EEP, you can associate more than one Kubernetes clusters to your
+With GitLab Premium, you can associate more than one Kubernetes clusters to your
 project. That way you can have different clusters for different environments,
 like dev, staging, production, etc.
 
@@ -249,9 +249,9 @@ and [add a cluster](#adding-a-cluster) again.
 
 Here's what you can do with GitLab if you enable the Kubernetes integration.
 
-### Deploy Boards (EEP)
+### Deploy Boards
 
-> Available in [GitLab Enterprise Edition Premium][ee].
+> Available in [GitLab Premium][ee].
 
 GitLab's Deploy Boards offer a consolidated view of the current health and
 status of each CI [environment](../../../ci/environments.md) running on Kubernetes,
@@ -261,9 +261,9 @@ workflow they already use without any need to access Kubernetes.
 
 [> Read more about Deploy Boards](../deploy_boards.md)
 
-### Canary Deployments (EEP)
+### Canary Deployments
 
-> Available in [GitLab Enterprise Edition Premium][ee].
+> Available in [GitLab Premium][ee].
 
 Leverage [Kubernetes' Canary deployments](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments)
 and visualize your canary deployments right inside the Deploy Board, without
@@ -303,4 +303,4 @@ the deployment variables above, ensuring any pods you create are labelled with
 `app=$CI_ENVIRONMENT_SLUG`. GitLab will do the rest!
 
 [permissions]: ../../permissions.md
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/user/project/deploy_boards.md

 # Deploy Boards
 
-> [Introduced][ee-1589] in [GitLab Enterprise Edition Premium][ee] 9.0.
+> [Introduced][ee-1589] in [GitLab Premium][ee] 9.0.
 
 GitLab's Deploy Boards offer a consolidated view of the current health and
 status of each CI [environment] running on [Kubernetes], displaying the status
@@ -104,7 +104,7 @@ version of your application.
 - [Kubernetes deploy example][kube-deploy]
 
 [ee-1589]: https://gitlab.com/gitlab-org/gitlab-ee/issues/1589 "Deploy Boards initial issue"
-[ee]: https://about.gitlab.com/gitlab-ee/ "GitLab Enterprise Edition landing page"
+[ee]: https://about.gitlab.com/products/ "GitLab Enterprise Edition landing page"
 [kube-deploy]: https://gitlab.com/gitlab-examples/kubernetes-deploy "Kubernetes deploy example project"
 [kubernetes]: https://kubernetes.io "Kubernetes website"
 [environment]: ../../ci/environments.md "Environments and deployments documentation"

doc/user/project/file_lock.md

 # File Locking
 
 >**Notes:**
-- [Introduced][ee-440] in [GitLab Enterprise Edition Premium][ee] 8.9.
+- [Introduced][ee-440] in [GitLab Premium][ee] 8.9.
 - This feature needs to have a license with the "File Lock" option enabled. If
-  you are using Enterprise Edition Premium but you don't see the "Lock" button,
+  you are using Premium but you don't see the "Lock" button,
   ask your GitLab administrator.
 
 File Locking helps you avoid merge conflicts and better manage your binary files.
@@ -14,7 +14,7 @@ member of the team can edit it.
 
 Working with multiple people on the same file can be a risk. Conflicts
 when merging a non-text file are hard to overcome and will require a lot
-of manual work to resolve. With GitLab Enterprise Edition Premium, File
+of manual work to resolve. With GitLab Premium, File
 Locking helps you avoid merge conflicts and better manage your binary
 files by preventing everyone, except you, from modifying a specific file
 or entire directory.
@@ -103,5 +103,5 @@ locks and [remove the ones you have permission for](#permissions-on-file-locking
 ![Locked Files](img/file_lock_list.png)
 
 [ee-440]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/440 "File Lock"
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [push access]: ../../user/permissions.md

doc/user/project/index.md

@@ -15,6 +15,9 @@ When you create a project in GitLab, you'll have access to a large number of
 
 **Repositories:**
 
+- [Issue tracker](issues/index.md): Discuss implementations with your team within issues
+  - [Issue Boards](issue_board.md): Organize and prioritize your workflow
+  - [Multiple Issue Boards](issue_board.md#multiple-issue-boards) (**Starter/Premium**): Allow your teams to create their own workflows (Issue Boards) for the same project
 - [Repositories](repository/index.md): Host your code in a fully
 integrated platform
   - [Branches](repository/branches/index.md): use Git branching strategies to
@@ -24,16 +27,16 @@ integrated platform
   - [Protected tags](protected_tags.md): Control over who has
   permission to create tags, and prevent accidental update or deletion
   - [Signing commits](gpg_signed_commits/index.md): use GPG to sign your commits
-- **(EEU)** [Web IDE](web_ide/index.md)
+- **(Ultimate)** [Web IDE](web_ide/index.md)
 
 **Issues and merge requests:**
 
 - [Issue tracker](issues/index.md): Discuss implementations with your team within issues
   - [Issue Boards](issue_board.md): Organize and prioritize your workflow
-  - [Multiple Issue Boards](https://docs.gitlab.com/ee/user/project/issue_board.html#multiple-issue-boards) (**EES/EEP**): Allow your teams to create their own workflows (Issue Boards) for the same project
+  - [Multiple Issue Boards](issue_board.md#multiple-issue-boards) (**Starter/Premium**): Allow your teams to create their own workflows (Issue Boards) for the same project
 - [Merge Requests](merge_requests/index.md): Apply your branching
 strategy and get reviewed by your team
-  - [Merge Request Approvals](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html) (**EES/EEP**): Ask for approval before
+  - [Merge Request Approvals](merge_requests/merge_request_approvals.md) (**Starter/Premium**): Ask for approval before
   implementing a change
   - [Fix merge conflicts from the UI](merge_requests/resolve_conflicts.md):
   Your Git diff tool right from GitLab's UI

doc/user/project/integrations/kubernetes.md

@@ -81,9 +81,9 @@ GitLab CI/CD build environment:
 
 Here's what you can do with GitLab if you enable the Kubernetes integration.
 
-### Deploy Boards (EEP)
+### Deploy Boards
 
-> Available in [GitLab Enterprise Edition Premium][ee].
+> Available in [GitLab Premium][ee].
 
 GitLab's Deploy Boards offer a consolidated view of the current health and
 status of each CI [environment](../../../ci/environments.md) running on Kubernetes,
@@ -93,9 +93,9 @@ workflow they already use without any need to access Kubernetes.
 
 [> Read more about Deploy Boards](https://docs.gitlab.com/ee/user/project/deploy_boards.html)
 
-### Canary Deployments (EEP)
+### Canary Deployments
 
-> Available in [GitLab Enterprise Edition Premium][ee].
+> Available in [GitLab Premium][ee].
 
 Leverage [Kubernetes' Canary deployments](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#canary-deployments)
 and visualize your canary deployments right inside the Deploy Board, without
@@ -134,4 +134,4 @@ containers. To use this integration, you should deploy to Kubernetes using
 the deployment variables above, ensuring any pods you create are labelled with
 `app=$CI_ENVIRONMENT_SLUG`. GitLab will do the rest!
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/user/project/issue_board.md

@@ -34,7 +34,7 @@ and deploy from one single platform. Issue Boards help you to visualize
 and manage the entire process _in_ GitLab.
 
 With [Multiple Issue Boards](#multiple-issue-boards), available
-only in [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/),
+only in [GitLab Enterprise Edition](https://about.gitlab.com/products/),
 you go even further, as you can not only keep yourself and your project
 organized from a broader perspective with one Issue Board per project,
 but also allow your team members to organize their own workflow by creating
@@ -72,7 +72,7 @@ beginning of the development lifecycle until deployed to production
 ### Use cases for Multiple Issue Boards
 
 With [Multiple Issue Boards](#multiple-issue-boards), available only in
-[GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/),
+[GitLab Enterprise Edition](https://about.gitlab.com/products/),
 each team can have their own board to organize their workflow individually.
 
 #### Scrum team
@@ -347,7 +347,7 @@ A few things to remember:
   20 will appear.
 
 [ce-5554]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5554
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [labels]: ./labels.md
 [scrum]: https://en.wikipedia.org/wiki/Scrum_(software_development)
 [kanban]: https://en.wikipedia.org/wiki/Kanban_(development)

doc/user/project/issues/create_new_issue.md

@@ -43,7 +43,7 @@ Enable [Service Desk](../service_desk.md) to your project and offer email suppor
 By doing so, when your customer sends a new email, a new issue can be created in
 the appropriate project and followed up from there.
 
-_Service Desk is available only for [GitLab Enterprise Edition Premium](https://about.gitlab.com/gitlab-ee/)
+_Service Desk is available only for [GitLab Premium](https://about.gitlab.com/products/)
 and [GitLab.com Silver](https://about.gitlab.com/gitlab-com/) subscribers._
 
 ## New issue from the group-level Issue Tracker

doc/user/project/issues/csv_export.md

 # Export Issues to CSV
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1126) in [GitLab Enterprise Edition Starter 9.0](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#export-issues-ees-eep).
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1126) in [GitLab Starter 9.0](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#export-issues-ees-eep).
 
 Issues can be exported as CSV from GitLab and are sent to your default notification email as an attachment.
 
@@ -38,7 +38,7 @@ You will be asked to confirm the number of issues and email address for the expo
 
 ## Format
 
-> **Time Estimate** and **Time Spent** columns were [introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2627) in GitLab Enterprise Edition Starter 10.0.
+> **Time Estimate** and **Time Spent** columns were [introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2627) in GitLab Starter 10.0.
 
 Data will be encoded with a comma as the column delimiter, with `"` used to quote fields if needed, and newlines to separate rows. The first row will be the headers, which are listed in the following table along with a description of the values:
 

doc/user/project/issues/index.md

@@ -35,7 +35,7 @@ your project public, open to collaboration.
 ### Streamline collaboration
 
 With [Multiple Assignees for Issues](multiple_assignees_for_issues.md),
-available in [GitLab Enterprise Edition Starter](https://about.gitlab.com/gitlab-ee/)
+available in [GitLab Starter](https://about.gitlab.com/products/)
 you can streamline collaboration and allow shared responsibilities to be clearly displayed.
 All assignees are shown across your workflows and receive notifications (as they
 would as single assignees), simplifying communication and ownership.
@@ -141,13 +141,19 @@ Find GitLab Issue Boards by navigating to your **Project's Dashboard** > **Issue
 Read through the documentation for [Issue Boards](../issue_board.md)
 to find out more about this feature.
 
-### Export Issues to CSV (EES/EEP)
+### Export Issues to CSV
+
+> Available in [GitLab Starter](https://about.gitlab.com/products/) and
+[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
 
 Issues can be [exported as CSV](csv_export.md) from GitLab and are sent to your email as an attachment.
 
-_Exporting issues to CSV is available only in [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/)._
+_Exporting issues to CSV is available only in [GitLab Enterprise Edition](https://about.gitlab.com/products/)._
+
+## Related Issues
 
-## Related Issues (EES/EEP)
+> Available in [GitLab Starter](https://about.gitlab.com/products/) and
+[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
 
 Related Issues are a bi-directional relationship between any two issues
 and appear in a block below the issue description. Issues can be across groups

doc/user/project/issues/issues_functionalities.md

@@ -41,7 +41,10 @@ it's reassigned to someone else to take it from there.
 if a user is not member of that project, it can only be
 assigned to them if they created the issue themselves.
 
-##### 3.1. Multiple Assignees (EES/EEP)
+##### 3.1. Multiple Assignees
+
+> Available in [GitLab Starter](https://about.gitlab.com/products/) and
+[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
 
 Often multiple people likely work on the same issue together,
 which can especially be difficult to track in large teams
@@ -86,9 +89,10 @@ but they are immediately available to all projects in the group.
 > **Tip:**
 if the label doesn't exist yet, when you click **Edit**, it opens a dropdown menu from which you can select **Create new label**.
 
-#### 8. Weight (EES/EEP)
+#### 8. Weight
 
-Issue Weights are only available in [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/).
+> Available in [GitLab Starter](https://about.gitlab.com/products/) and
+[GitLab.com Bronze](https://about.gitlab.com/gitlab-com/).
 
 - Attribute a weight (in a 0 to 9 range) to that issue. Easy to complete
 should weight 1 and very hard to complete should weight 9.

doc/user/project/issues/multiple_assignees_for_issues.md

@@ -2,7 +2,7 @@
 
 > **Note:**
 [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/1904)
-in [GitLab Enterprise Edition Starter 9.2](https://about.gitlab.com/2017/05/22/gitlab-9-2-released/#multiple-assignees-for-issues).
+in [GitLab Starter 9.2](https://about.gitlab.com/2017/05/22/gitlab-9-2-released/#multiple-assignees-for-issues).
 
 ## Overview
 
@@ -10,7 +10,7 @@ In large teams, where there is shared ownership of an issue, it can be difficult
 to track who is working on it, who already completed their contributions, who
 didn't even start yet.
 
-In [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/),
+In [GitLab Enterprise Edition](https://about.gitlab.com/products/),
 you can also select multiple assignees to an issue, making it easier to
 track, and making clearer who is accountable for it.
 

doc/user/project/issues/related_issues.md

 # Related issues
 
-> [Introduced][ee-1797] in [GitLab Enterprise Edition Starter][ee] 9.4.
+> [Introduced][ee-1797] in [GitLab Starter][ee] 9.4.
 
 Related issues are a bi-directional relationship between any two issues
 and appear in a block below the issue description. Issues can be across groups
@@ -31,7 +31,7 @@ Please access our [permissions] page for more information.
 
 As an addition, you are also able to manage related issues through [our API].
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [ee-1797]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1797
 [permissions]: ../../permissions.md
 [Our API]: ../../../api/issue_links.md

doc/user/project/merge_requests/browser_performance_testing.md

 # Browser Performance Testing
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3507) in [GitLab Enterprise Edition Premium](https://about.gitlab.com/gitlab-ee/) 10.3.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3507) in [GitLab Premium](https://about.gitlab.com/products/) 10.3.
 
 ## Overview
 

doc/user/project/merge_requests/code_quality_diff.md

 # Code Quality
 
-> [Introduced][ee-1984] in [GitLab Enterprise Edition Starter][ee] 9.3.
+> [Introduced][ee-1984] in [GitLab Starter][ee] 9.3.
 
 ## Overview
 
@@ -28,7 +28,7 @@ For instance, consider the following workflow:
 ## How it works
 
 >**Note:**
-In [GitLab Enterprise Edition Starter][ee] 10.0, another job name will
+In [GitLab Starter][ee] 10.0, another job name will
 also be supported: `codequality`. This new job name will eventually replace
 `codeclimate` which is scheduled to be removed in GitLab 11.0. You are advised
 to update your current `.gitlab-ci.yml` configuration to reflect that change.
@@ -49,7 +49,7 @@ For more information on how the `codequality` job should look like, check the
 example on [analyzing a project's code quality with Code Climate CLI][cc-docs].
 
 [ee-1984]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1984
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [ci]: ../../../ci/README.md
 [cc]: https://codeclimate.com
 [cd]: https://hub.docker.com/r/codeclimate/codeclimate/

doc/user/project/merge_requests/dast.md

 # Dynamic Application Security Testing (DAST)
 
-> [Introduced][ee-4348] in [GitLab Enterprise Edition Ultimate][ee] 10.4.
+> [Introduced][ee-4348] in [GitLab Ultimate][ee] 10.4.
 
 If you are using [GitLab CI/CD][ci], you can analyze your running web application(s)
 for known vulnerabilities using Dynamic Application Security Testing (DAST).
@@ -52,6 +52,6 @@ see the details and the URL(s) affected.
 ![DAST Widget Clicked](img/dast_single.png)
 
 [ee-4348]: https://gitlab.com/gitlab-org/gitlab-ee/issues/4348
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [ci]: ../../../ci/README.md
 [cc-docs]: ../../../ci/examples/dast.md

doc/user/project/merge_requests/index.md

@@ -31,11 +31,11 @@ With GitLab merge requests, you can:
 
 With **[GitLab Enterprise Edition][ee]**, you can also:
 
-- View the deployment process across projects with [Multi-Project Pipeline Graphs](../../../ci/multi_project_pipeline_graphs.md) (available only in GitLab Enterprise Edition Premium)
-- Request [approvals](#merge-request-approvals) from your managers (available in GitLab Enterprise Edition Starter)
-- [Squash and merge](#squash-and-merge) for a cleaner commit history (available in GitLab Enterprise Edition Starter)
-- Analyze the impact of your changes with [Code Quality reports](#code-quality-reports) (available in GitLab Enterprise Edition Starter)
-- Determine the performance impact of changes with [Browser Performance Testing](#browser-performance-testing) (available in GitLab Enterprise Edition Premium)
+- View the deployment process across projects with [Multi-Project Pipeline Graphs](../../../ci/multi_project_pipeline_graphs.md) (available only in GitLab Premium)
+- Request [approvals](#merge-request-approvals) from your managers (available in GitLab Starter)
+- [Squash and merge](#squash-and-merge) for a cleaner commit history (available in GitLab Starter)
+- Analyze the impact of your changes with [Code Quality reports](#code-quality-reports) (available in GitLab Starter)
+- Determine the performance impact of changes with [Browser Performance Testing](#browser-performance-testing) (available in GitLab Premium)
 
 ## Use cases
 
@@ -180,7 +180,7 @@ have been marked as a **Work In Progress**.
 
 ## Merge request approvals
 
-> Included in [GitLab Enterprise Edition Starter][products].
+> Included in [GitLab Starter][products].
 
 If you want to make sure every merge request is approved by one or more people,
 you can enforce this workflow by using merge request approvals. Merge request
@@ -191,7 +191,7 @@ list of approvers that will need to approve every merge request in a project.
 
 ## Code Quality reports
 
-> Introduced in [GitLab Enterprise Edition Starter][products] 9.3.
+> Introduced in [GitLab Starter][products] 9.3.
 
 If you are using [GitLab CI][ci], you can analyze your source code quality using
 the [Code Climate][cc] analyzer [Docker image][cd]. Going a step further, GitLab
@@ -201,7 +201,7 @@ can show the Code Climate report right in the merge request widget area.
 
 ## Static Application Security Testing
 
-> Introduced in [GitLab Enterprise Edition Ultimate][products] 10.3.
+> Introduced in [GitLab Ultimate][products] 10.3.
 
 If you are using [GitLab CI/CD][ci], you can analyze your source code for known
 vulnerabilities using Static Application Security Testing (SAST).
@@ -212,7 +212,7 @@ merge request widget area.
 
 ## Static Application Security Testing for Docker containers
 
-> Introduced in [GitLab Enterprise Edition Ultimate][products] 10.4.
+> Introduced in [GitLab Ultimate][products] 10.4.
 
 If you are using [GitLab CI/CD][ci], you can analyze your Docker images for known
 vulnerabilities.
@@ -223,7 +223,7 @@ merge request widget area.
 
 ## Browser Performance Testing
 
-> Introduced in [GitLab Enterprise Edition Premium][products] 10.3.
+> Introduced in [GitLab Premium][products] 10.3.
 
 If your application offers a web interface and you are using [GitLab CI/CD][ci], you can quickly determine the performance impact of pending code changes. GitLab uses [Sitespeed.io][sitespeed], a free and open source tool for measuring the performance of web sites, to analyze the performance of specific pages.
 
@@ -361,6 +361,6 @@ git checkout origin/merge-requests/1
 [ci]: ../../../ci/README.md
 [cc]: https://codeclimate.com/
 [cd]: https://hub.docker.com/r/codeclimate/codeclimate/
-[ee]: https://about.gitlab.com/gitlab-ee/ "GitLab Enterprise Edition"
+[ee]: https://about.gitlab.com/products/ "GitLab Enterprise Edition"
 [sitespeed]: https://www.sitespeed.io
 [sitespeed-container]: https://hub.docker.com/r/sitespeedio/sitespeed.io/

doc/user/project/merge_requests/merge_request_approvals.md

 # Merge request approvals
 
-> Introduced in [GitLab Enterprise Edition 7.12](https://about.gitlab.com/2015/06/22/gitlab-7-12-released/#merge-request-approvers-ee-only), available in [GitLab Enterprise Edition Starter](https://about.gitlab.com/gitlab-ee/).
+> Introduced in [GitLab Enterprise Edition 7.12](https://about.gitlab.com/2015/06/22/gitlab-7-12-released/#merge-request-approvers-ee-only), available in [GitLab Starter](https://about.gitlab.com/products/).
 
 ## Overview
 

doc/user/project/merge_requests/sast.md

 # Static Application Security Testing (SAST)
 
-> [Introduced][ee-3775] in [GitLab Enterprise Edition Ultimate][ee] 10.3.
+> [Introduced][ee-3775] in [GitLab Ultimate][ee] 10.3.
 
 ## Overview
 
@@ -38,6 +38,6 @@ For more information on how the `sast` job should look like, check the
 [example on analyzing a project's code for vulnerabilities][cc-docs].
 
 [ee-3775]: https://gitlab.com/gitlab-org/gitlab-ee/issues/3775
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [ci]: ../../../ci/README.md
 [cc-docs]: ../../../ci/examples/sast.md

doc/user/project/merge_requests/sast_docker.md

 # Static Application Security Testing for Docker containers
 
-> [Introduced][ee-3672] in [GitLab Enterprise Edition Ultimate][ee] 10.4.
+> [Introduced][ee-3672] in [GitLab Ultimate][ee] 10.4.
 
 ## Overview
 
@@ -38,6 +38,6 @@ For more information on how the `sast:container` job should look like, check the
 example on [analyzing a Docker image for vulnerabilities][cc-docs].
 
 [ee-3672]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3672
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [ci]: ../../../ci/README.md
 [cc-docs]: ../../../ci/examples/sast_docker.md

doc/user/project/merge_requests/squash_and_merge.md

 # Squash and merge
 
-> [Introduced][ee-1024] in [GitLab Enterprise Edition Starter][ee] 8.17.
+> [Introduced][ee-1024] in [GitLab Starter][ee] 8.17.
 
 Combine all commits of your merge request into one and retain a clean history.
 
@@ -74,5 +74,5 @@ squashing can itself be considered equivalent to rebasing.
 [squash-edit-form]: img/squash_edit_form.png
 [squash-mr-widget]: img/squash_mr_widget.png
 [ff-merge]: fast_forward_merge.md#enabling-fast-forward-merges
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [revert]: revert_changes.md

doc/user/project/milestones/burndown_charts.md

 # Burndown Charts
 
 >**Notes:**
-- [Introduced][ee-1540] in [GitLab Enterprise Edition Starter 9.1][ee-9.1].
+- [Introduced][ee-1540] in [GitLab Starter 9.1][ee-9.1].
 - Closed or reopened issues prior to GitLab 9.1 won't have a `closed_at`
   value, so the burndown chart considers them as closed on the milestone
   `start_date`. In that case, a warning will be displayed.
@@ -16,7 +16,7 @@ At a glance, you see the current state for the completion a given milestone.
 Without them, you would have to organize the data from the milestone and plot it
 yourself to have the same sense of progress.
 
-GitLab Enterprise Edition Starter plots it for you and presents it in a clear and beautiful chart.
+GitLab Starter plots it for you and presents it in a clear and beautiful chart.
 
 For an overview, check the video demonstration on [Mapping Work Versus Time, With Burndown Charts](https://about.gitlab.com/2017/04/25/mapping-work-to-do-versus-time-with-burndown-charts/).
 

doc/user/project/milestones/index.md

@@ -16,7 +16,7 @@ Milestones are a valuable tool to track the development of the process of achiev
 From a milestone, you view the status of issues and merge requests, its contributors,
 and opened and closed issues for each label.
 
-With [GitLab Enterprise Edition Starter](https://about.gitlab.com/gitlab-ee/),
+With [GitLab Starter](https://about.gitlab.com/products/),
 you will also see a [Burndown Chart](#burndown-charts) for your milestone, which
 gives a visual insight over the progress of the conclusion of that milestone:
 
@@ -90,7 +90,7 @@ total merge requests and issues.
 ## Burndown Charts
 
 [Burndown Charts](burndown_charts.md), available in
-[GitLab Enterprise Edition Starter](https://about.gitlab.com/gitlab-ee),
+[GitLab Starter](https://about.gitlab.com/products),
 are visual representations of the progress of completing a milestone.
 
 ![burndown chart](img/burndown_chart.png)

doc/user/project/protected_branches.md

@@ -68,7 +68,7 @@ they are set to "Masters" by default.
 
 ## Restricting push and merge access to certain users
 
-> This feature was [introduced][ce-5081] in [GitLab Enterprise Edition Starter][ee] 8.11.
+> This feature was [introduced][ce-5081] in [GitLab Starter][ee] 8.11.
 
 With GitLab Enterprise Edition you can restrict access to protected branches
 by choosing a role (Masters, Developers) as well as certain users. From the
@@ -159,4 +159,4 @@ for details about the pipelines security model.
 [ce-21393]: https://gitlab.com/gitlab-org/gitlab-ce/issues/21393
 [ee-restrict]: http://docs.gitlab.com/ee/user/project/protected_branches.html#restricting-push-and-merge-access-to-certain-users
 [perm]: ../permissions.md
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/user/project/quick_actions.md

@@ -45,5 +45,5 @@ do.
 | `/tableflip`	             | Append the comment with `(╯°□°)╯︵ ┻━┻` |
 | `/shrug`	                 | Append the comment with `¯\＿(ツ)＿/¯` |
 
-Note: In GitLab EES every issue can have more than one assignee, so commands `/assign`, `/unassign` and `/reassign`
+Note: In GitLab Starter every issue can have more than one assignee, so commands `/assign`, `/unassign` and `/reassign`
 support multiple assignees.

doc/user/project/repository/index.md

@@ -66,7 +66,7 @@ your implementation with your team.
 You can live preview changes submitted to a new branch with
 [Review Apps](../../../ci/review_apps/index.md).
 
-With [GitLab Enterprise Edition](https://about.gitlab.com/gitlab-ee/)
+With [GitLab Enterprise Edition](https://about.gitlab.com/products/)
 subscriptions, you can also request
 [approval](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html#merge-request-approvals) from your managers.
 
@@ -147,12 +147,14 @@ Select branches to compare and view the changes inline:
 
 Find it under your project's **Repository > Compare**.
 
-## Locked files (EEP)
+## Locked files
+
+> Available in [GitLab Premium](https://about.gitlab.com/products/).
 
 Lock your files to prevent any conflicting changes.
 
 [File Locking](https://docs.gitlab.com/ee/user/project/file_lock.html) is available only in
-[GitLab Enterprise Edition Premium](https://about.gitlab.com/gitlab-ee/).
+[GitLab Premium](https://about.gitlab.com/products/).
 
 ## Repository's API
 

doc/user/project/service_desk.md

 # Service Desk
 
-> [Introduced][ee-149] in [GitLab Enterprise Edition Premium 9.1][eep-9.1].
+> [Introduced][ee-149] in [GitLab Premium 9.1][eep-9.1].
 
 ## Overview
 
@@ -57,7 +57,7 @@ you can skip the step 1 below; you only need to enable it per project.
      support [email sub-addressing][email-sub-addressing].
 2.   Navigate to your project's **Settings** and scroll down to the **Service Desk**
      section.
-3.   If you have the correct access and an Enterprise Edition Premium license,
+3.   If you have the correct access and an Premium license,
      you will see an option to set up Service Desk:
 
      ![Activate Service Desk option](img/service_desk_disabled.png)
@@ -117,7 +117,7 @@ Behind the scenes, Service Desk works by the special Support Bot user creating i
 does not count toward the license limit count.
 
 [ee-149]: https://gitlab.com/gitlab-org/gitlab-ee/issues/149 "Service Desk with email"
-[ee]: https://about.gitlab.com/gitlab-ee/ "GitLab Enterprise Edition landing page"
+[ee]: https://about.gitlab.com/products/ "GitLab Enterprise Edition landing page"
 [eep-9.1]: https://about.gitlab.com/2017/04/22/gitlab-9-1-released/#service-desk-eep
 [reply-by-email]: ../../administration/reply_by_email.md#set-it-up
 [email-sub-addressing]: ../../administration/reply_by_email.md#email-sub-addressing

doc/user/project/settings/index.md

@@ -34,7 +34,7 @@ Set up your project's merge request settings:
 
 - Set up the merge request method (merge commit, [fast-forward merge](../merge_requests/fast_forward_merge.html)).
 - Merge request [description templates](../description_templates.md#description-templates).
-- Enable [merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html#merge-request-approvals), _available in [GitLab Enterprise Edition Starter](https://about.gitlab.com/gitlab-ee/)_.
+- Enable [merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html#merge-request-approvals), _available in [GitLab Starter](https://about.gitlab.com/products/)_.
 - Enable [merge only of pipeline succeeds](../merge_requests/merge_when_pipeline_succeeds.md).
 - Enable [merge only when all discussions are resolved](../../discussions/index.md#only-allow-merge-requests-to-be-merged-if-all-discussions-are-resolved).
 
@@ -42,7 +42,7 @@ Set up your project's merge request settings:
 
 ### Service Desk
 
-Enable [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html) for your project to offer customer support. Service Desk is available in [GitLab Enterprise Edition Premium](https://about.gitlab.com/gitlab-ee/).
+Enable [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html) for your project to offer customer support. Service Desk is available in [GitLab Premium](https://about.gitlab.com/products/).
 
 ### Export project
 

doc/user/project/web_ide/index.md

 # Web IDE
 
-> Introduced in [GitLab Enterprise Edition Ultimate][ee] 10.4.
+> Introduced in [GitLab Ultimate][ee] 10.4.
 
 > **Warning:** Web IDE is in **Beta**. For the latest updates, check the
 > associated [epic](https://gitlab.com/groups/gitlab-org/-/epics/26).
@@ -32,4 +32,4 @@ the 'Commit Button'.
 
 ![Commit changes](img/commit_changes.png)
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/user/search/advanced_global_search.md

 # Advanced Global Search
 
 >
-- [Introduced][ee-109] in GitLab [Enterprise Edition Starter][ee] 8.4.
+- [Introduced][ee-109] in GitLab [Starter][ee] 8.4.
 - This is the user documentation. To install and configure Elasticsearch,
   visit the [admin docs](../../integration/elasticsearch.md).
 
@@ -69,5 +69,5 @@ search even if Elasticsearch is enabled.
 [install]: https://www.elastic.co/guide/en/elasticsearch/reference/current/_installation.html "Elasticsearch installation documentation"
 [pkg]: https://about.gitlab.com/downloads/ "Download Omnibus GitLab"
 [elastic-settings]: https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-configuration.html#settings "Elasticsearch configuration settings"
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [es]: https://www.elastic.co/products/elasticsearch

doc/user/search/advanced_search_syntax.md

@@ -43,5 +43,5 @@ here's a quick guide:
 * To match a partial word, use `*`: `bug find_by_*`
 * To find a term containing one of these symbols, use `\`: `argument \-last`
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/
 [elastic]: https://www.elastic.co/guide/en/elasticsearch/reference/5.3/query-dsl-simple-query-string-query.html#_simple_query_string_syntax

doc/user/search/index.md

@@ -146,4 +146,4 @@ Use advanced queries for more targeted search results.
 
 [Learn how to use the Advanced Syntax Search.](advanced_search_syntax.md)
 
-[ee]: https://about.gitlab.com/gitlab-ee/
+[ee]: https://about.gitlab.com/products/

doc/workflow/issue_weight.md

 # Issue Weight
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/76)
-in [GitLab Enterprise Edition Starter](https://about.gitlab.com/gitlab-ee/) 8.3.
+in [GitLab Starter](https://about.gitlab.com/products/) 8.3.
 
 When you have a lot of issues, it can be hard to get an overview.
 By adding a weight to each issue, you can get a better idea of how much time,

doc/workflow/lfs/lfs_administration.md

@@ -47,7 +47,7 @@ In `config/gitlab.yml`:
 
 ## Setting up S3 compatible object storage
 
-> **Note:** [Introduced][ee-2760] in [GitLab Enterprise Edition Premium][eep] 10.0.
+> **Note:** [Introduced][ee-2760] in [GitLab Premium][eep] 10.0.
 
 It is possible to store LFS objects on remote object storage instead of on a local disk.
 
@@ -161,5 +161,5 @@ and [projects APIs](../../api/projects.md).
 
 [reconfigure gitlab]: ../../administration/restart_gitlab.md#omnibus-gitlab-reconfigure "How to reconfigure Omnibus GitLab"
 [restart gitlab]: ../../administration/restart_gitlab.md#installations-from-source "How to restart GitLab"
-[eep]: https://about.gitlab.com/gitlab-ee/ "GitLab Enterprise Edition Premium"
+[eep]: https://about.gitlab.com/products/ "GitLab Premium"
 [ee-2760]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2760

doc/workflow/repository_mirroring.md

@@ -120,7 +120,7 @@ or by changing the import URL in repository settings.
 
 ### SSH authentication
 
-> [Introduced][ee-2551] in GitLab Enterprise Edition Starter 9.5
+> [Introduced][ee-2551] in GitLab Starter 9.5
 
 If you're mirroring over SSH (i.e., an `ssh://` URL), you can authenticate using
 password-based authentication, just as over HTTPS, but you can also use public