Change docs links to https://about.gitlab.com/products/

5b54e260 · Achilleas Pipinellis · dde26697 · 5b54e260 · 5b54e260 · 5b54e260
Commit 5b54e260 authored Feb 07, 2018 by Achilleas Pipinellis
57 changed files
--- a/doc/administration/audit_events.md
+++ b/doc/administration/audit_events.md
@@ -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
--- a/doc/administration/auditor_users.md
+++ b/doc/administration/auditor_users.md
@@ -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
--- a/doc/administration/auth/how_to_configure_ldap_gitlab_ee/index.md
+++ b/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.

--- a/doc/administration/database_load_balancing.md
+++ b/doc/administration/database_load_balancing.md
@@ -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)

--- a/doc/administration/high_availability/database.md
+++ b/doc/administration/high_availability/database.md
@@ -6,7 +6,7 @@ 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 Premium](https://about.gitlab.com/gitlab-ee/), using the Omnibus GitLab package.
+- 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.

--- a/doc/administration/index.md
+++ b/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

--- a/doc/administration/job_artifacts.md
+++ b/doc/administration/job_artifacts.md
@@ -284,7 +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 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
--- a/doc/administration/operations/fast_ssh_key_lookup.md
+++ b/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.

--- a/doc/api/jobs.md
+++ b/doc/api/jobs.md
@@ -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
--- a/doc/api/projects.md
+++ b/doc/api/projects.md
@@ -1335,7 +1335,7 @@ POST /projects/:id/housekeeping
 ## Push Rules
 >**Note:**
-Available in [GitLab 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 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

--- a/doc/ci/examples/browser_performance.md
+++ b/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 Premium](https://about.gitlab.com/gitlab-ee/) users, a performance score 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

--- a/doc/ci/examples/code_climate.md
+++ b/doc/ci/examples/code_climate.md
@@ -31,4 +31,4 @@ 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/
--- a/doc/ci/examples/dast.md
+++ b/doc/ci/examples/dast.md
@@ -37,4 +37,4 @@ 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/
--- a/doc/ci/examples/sast.md
+++ b/doc/ci/examples/sast.md
@@ -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/
--- a/doc/ci/examples/sast_docker.md
+++ b/doc/ci/examples/sast_docker.md
@@ -52,4 +52,4 @@ 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/
--- a/doc/ci/pipelines.md
+++ b/doc/ci/pipelines.md
@@ -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 Premium"
+[eep]: https://about.gitlab.com/products/ "GitLab Premium"
 [ee-2121]: https://gitlab.com/gitlab-org/gitlab-ee/issues/2121
--- a/doc/ci/triggers/README.md
+++ b/doc/ci/triggers/README.md
@@ -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

--- a/doc/gitlab-geo/README.md
+++ b/doc/gitlab-geo/README.md
@@ -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"
--- a/doc/gitlab-geo/docker_registry.md
+++ b/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/
--- a/doc/integration/elasticsearch.md
+++ b/doc/integration/elasticsearch.md
@@ -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/
--- a/doc/integration/jira_development_panel.md
+++ b/doc/integration/jira_development_panel.md
@@ -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
--- a/doc/integration/kerberos.md
+++ b/doc/integration/kerberos.md
@@ -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/
--- a/doc/push_rules/push_rules.md
+++ b/doc/push_rules/push_rules.md
@@ -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/
--- a/doc/tools/email.md
+++ b/doc/tools/email.md
@@ -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/
--- a/doc/topics/autodevops/index.md
+++ b/doc/topics/autodevops/index.md
@@ -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/
--- a/doc/user/group/contribution_analytics/index.md
+++ b/doc/user/group/contribution_analytics/index.md
@@ -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/
--- a/doc/user/group/epics/index.md
+++ b/doc/user/group/epics/index.md
@@ -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
--- a/doc/user/group/index.md
+++ b/doc/user/group/index.md
@@ -300,4 +300,3 @@ 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 Premium"
--- a/doc/user/permissions.md
+++ b/doc/user/permissions.md
@@ -130,7 +130,7 @@ The user that locks a file or directory is the only one that can edit and push t
 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 Premium](https://about.gitlab.com/gitlab-ee/) only.
+[GitLab Premium](https://about.gitlab.com/products/) only.
 ### Confidential Issues permissions
@@ -288,7 +288,7 @@ Read through the documentation on [LDAP users permissions](../administration/aut
 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 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
@@ -302,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/
--- a/doc/user/project/canary_deployments.md
+++ b/doc/user/project/canary_deployments.md
@@ -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

--- a/doc/user/project/clusters/index.md
+++ b/doc/user/project/clusters/index.md
@@ -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/
--- a/doc/user/project/deploy_boards.md
+++ b/doc/user/project/deploy_boards.md
@@ -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"

--- a/doc/user/project/file_lock.md
+++ b/doc/user/project/file_lock.md
@@ -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
--- a/doc/user/project/issue_board.md
+++ b/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)

--- a/doc/user/project/issues/create_new_issue.md
+++ b/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 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

--- a/doc/user/project/issues/index.md
+++ b/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 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.
@@ -148,7 +148,7 @@ to find out more about this feature.
 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

--- a/doc/user/project/issues/multiple_assignees_for_issues.md
+++ b/doc/user/project/issues/multiple_assignees_for_issues.md
@@ -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.

--- a/doc/user/project/issues/related_issues.md
+++ b/doc/user/project/issues/related_issues.md
@@ -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
--- a/doc/user/project/merge_requests/browser_performance_testing.md
+++ b/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 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

--- a/doc/user/project/merge_requests/code_quality_diff.md
+++ b/doc/user/project/merge_requests/code_quality_diff.md
@@ -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/

--- a/doc/user/project/merge_requests/dast.md
+++ b/doc/user/project/merge_requests/dast.md
@@ -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
--- a/doc/user/project/merge_requests/index.md
+++ b/doc/user/project/merge_requests/index.md
@@ -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/
--- a/doc/user/project/merge_requests/merge_request_approvals.md
+++ b/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 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

--- a/doc/user/project/merge_requests/sast.md
+++ b/doc/user/project/merge_requests/sast.md
@@ -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
--- a/doc/user/project/merge_requests/sast_docker.md
+++ b/doc/user/project/merge_requests/sast_docker.md
@@ -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
--- a/doc/user/project/merge_requests/squash_and_merge.md
+++ b/doc/user/project/merge_requests/squash_and_merge.md
@@ -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
--- a/doc/user/project/milestones/index.md
+++ b/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 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 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)

--- a/doc/user/project/protected_branches.md
+++ b/doc/user/project/protected_branches.md
@@ -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/
--- a/doc/user/project/repository/index.md
+++ b/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.
@@ -154,7 +154,7 @@ Find it under your project's **Repository > Compare**.
 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 Premium](https://about.gitlab.com/gitlab-ee/).
+[GitLab Premium](https://about.gitlab.com/products/).
 ## Repository's API

--- a/doc/user/project/service_desk.md
+++ b/doc/user/project/service_desk.md
@@ -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

--- a/doc/user/project/settings/index.md
+++ b/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 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 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

--- a/doc/user/project/web_ide/index.md
+++ b/doc/user/project/web_ide/index.md
@@ -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/
--- a/doc/user/search/advanced_global_search.md
+++ b/doc/user/search/advanced_global_search.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
--- a/doc/user/search/advanced_search_syntax.md
+++ b/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
--- a/doc/user/search/index.md
+++ b/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/
--- a/doc/workflow/issue_weight.md
+++ b/doc/workflow/issue_weight.md
 # Issue Weight
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/76)
-in [GitLab 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,

--- a/doc/workflow/lfs/lfs_administration.md
+++ b/doc/workflow/lfs/lfs_administration.md
@@ -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 Premium"
+[eep]: https://about.gitlab.com/products/ "GitLab Premium"
 [ee-2760]: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2760