EE - search and replace "Enterprise Edition Starter" => "Starter"

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.

doc/administration/high_availability/database.md

@@ -7,7 +7,7 @@ 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.
+- If you are a Community Edition or Starter user, consider using a cloud hosted solution.
 - This document will not cover installations from source.
 
 >

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/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/gitlab-ee).
 
 ### 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/gitlab-ee).
 
 ```
 POST /projects/:id/mirror/pull

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

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.
 

doc/push_rules/push_rules.md

@@ -77,7 +77,7 @@ 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.

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.
 

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.
 

doc/user/project/index.md

@@ -27,7 +27,7 @@ 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:**
 

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/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
 

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

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.

doc/user/project/merge_requests/index.md

@@ -32,9 +32,9 @@ 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)
+- 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 Enterprise Edition 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

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/gitlab-ee/).
 
 ## Overview
 

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.
 

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/gitlab-ee/),
 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/gitlab-ee),
 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

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).
 

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/gitlab-ee/) 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/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