Fix broken anchor link

This broken anchor link was introduced yesterday, somewhere else.
Fixing so 'master' remains unbroken.

doc/administration/feature_flags.md

@@ -13,7 +13,7 @@ to deploy features in an early stage of development so that they can be
 incrementally rolled out.
 
 Before making them permanently available, features can be deployed behind
-flags for a [number of reasons](../development/feature_flags/process.md#when-to-use-feature-flags), such as:
+flags for a [number of reasons](../development/feature_flags/index.md#when-to-use-feature-flags), such as:
 
 - To test the feature.
 - To get feedback from users and customers while in an early stage of the development of the feature.

doc/api/graphql/getting_started.md

@@ -6,7 +6,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Getting started with GitLab GraphQL API
 
-This guide demonstrates basic usage of GitLab's GraphQL API.
+This guide demonstrates basic usage of the GitLab GraphQL API.
 
 See the [GraphQL API style guide](../../development/api_graphql_styleguide.md) for implementation details
 aimed at developers who wish to work on developing the API itself.
@@ -69,7 +69,7 @@ In the GitLab GraphQL API, `id` refers to a
 [Global ID](https://graphql.org/learn/global-object-identification/),
 which is an object identifier in the format of `"gid://gitlab/Issue/123"`.
 
-[GitLab's GraphQL Schema](reference/index.md) outlines which objects and fields are
+[GitLab GraphQL Schema](reference/index.md) outlines which objects and fields are
 available for clients to query and their corresponding data types.
 
 Example: Get only the names of all the projects the currently logged in user can access (up to a limit, more on that later)
@@ -289,7 +289,7 @@ More about introspection:
 
 ## Sorting
 
-Some of GitLab's GraphQL endpoints allow you to specify how you'd like a collection of
+Some of the GitLab GraphQL endpoints allow you to specify how you'd like a collection of
 objects to be sorted. You can only sort by what the schema allows you to.
 
 Example: Issues can be sorted by creation date:
@@ -314,7 +314,7 @@ Pagination is a way of only asking for a subset of the records (say, the first 1
 If we want more of them, we can make another request for the next 10 from the server
 (in the form of something like "please give me the next 10 records").
 
-By default, GitLab's GraphQL API returns only the first 100 records of any collection.
+By default, the GitLab GraphQL API returns only the first 100 records of any collection.
 This can be changed by using `first` or `last` arguments. Both arguments take a value,
 so `first: 10` returns the first 10 records, and `last: 10` the last 10 records.
 

doc/api/graphql/index.md

@@ -16,7 +16,7 @@ For those new to the GitLab GraphQL API, see
 
 ### Quick Reference
 
-- GitLab's GraphQL API endpoint is located at `/api/graphql`.
+- The GitLab GraphQL API endpoint is located at `/api/graphql`.
 - Get an [introduction to GraphQL from graphql.org](https://graphql.org/).
 - GitLab supports a wide range of resources, listed in the [GraphQL API Reference](reference/index.md).
 
@@ -115,9 +115,9 @@ library GitLab uses on the backend.
 
 ## Reference
 
-GitLab's GraphQL reference [is available](reference/index.md).
+The GitLab GraphQL reference [is available](reference/index.md).
 
-It is automatically generated from GitLab's GraphQL schema and embedded in a Markdown file.
+It is automatically generated from the GitLab GraphQL schema and embedded in a Markdown file.
 
 Machine-readable versions are also available:
 

doc/development/feature_flags/process.md

@@ -53,7 +53,6 @@ problems, such as outages.
 
 Please also read the [development guide for feature flags](development.md).
 
-
 ### Including a feature behind feature flag in the final release
 
 In order to build a final release and present the feature for self-managed

doc/user/project/issues/index.md

@@ -35,7 +35,7 @@ you can also view all the issues collectively at the group level.
 See also [Always start a discussion with an issue](https://about.gitlab.com/blog/2016/03/03/start-with-an-issue/).
 
 <i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
-To learn how the GitLab Strategic Marketing department uses GitLab issues with [labels](../labels.md) and
+To learn how our Strategic Marketing department uses GitLab issues with [labels](../labels.md) and
 [issue boards](../issue_board.md), see the video on
 [Managing Commitments with Issues](https://www.youtube.com/watch?v=cuIHNintg1o&t=3).