Removed parentheses around Optional

doc/install/relative_url.md

@@ -60,7 +60,7 @@ assumptions are made:
 
 Make sure to follow all steps below:
 
-1. (Optional) If you run short on resources, you can temporarily free up some
+1. Optional. If you run short on resources, you can temporarily free up some
    memory by shutting down the GitLab service with the following command:
 
    ```shell

doc/integration/bitbucket.md

@@ -42,7 +42,7 @@ to the end of the Bitbucket authorization callback URL.
 
    - **Name:** This can be anything. Consider something like `<Organization>'s GitLab`
      or `<Your Name>'s GitLab` or something else descriptive.
-   - **Application description:** *(Optional)* Fill this in if you wish.
+   - **Application description:** Optional. Fill this in if you wish.
    - **Callback URL:** (Required in GitLab versions 8.15 and greater)
      The URL to your GitLab installation, such as
      `https://gitlab.example.com/users/auth`.

doc/integration/datadog.md

@@ -32,15 +32,15 @@ project, group, or instance level:
 1. Scroll to **Add an integration**, and select **Datadog**.
 1. Select **Active** to enable the integration.
 1. Specify the [**Datadog site**](https://docs.datadoghq.com/getting_started/site/) to send data to.
-1. (Optional) To override the API URL used to send data directly, provide an **API URL**.
+1. Optional. To override the API URL used to send data directly, provide an **API URL**.
    Used only in advanced scenarios.
 1. Provide your Datadog **API key**.
-1. (Optional) If you use more than one GitLab instance, provide a unique **Service** name
+1. Optional. If you use more than one GitLab instance, provide a unique **Service** name
    to differentiate between your GitLab instances.
-1. (Optional) If you use groups of GitLab instances (such as staging and production
+1. Optional. If you use groups of GitLab instances (such as staging and production
    environments), provide an **Env** name. This value is attached to each span
    the integration generates.
-1. (Optional) Select **Test settings** to test your integration.
+1. Optional. Select **Test settings** to test your integration.
 1. Select **Save changes**.
 
 When the integration sends data, you can view it in the [CI Visibility](https://app.datadoghq.com/ci)

doc/integration/elasticsearch.md

@@ -279,8 +279,8 @@ To disable the Elasticsearch integration:
 1. On the top bar, select **Menu > Admin**.
 1. On the left sidebar, select **Settings > Advanced Search**.
 1. Uncheck **Elasticsearch indexing** and **Search with Elasticsearch enabled**.
-1. Click **Save changes** for the changes to take effect.
-1. (Optional) Delete the existing indexes:
+1. Select **Save changes**.
+1. Optional. Delete the existing indexes:
 
    ```shell
    # Omnibus installations

doc/operations/incident_management/integrations.md

@@ -65,11 +65,11 @@ and you can [customize the payload](#customize-the-alert-payload-outside-of-gitl
    1. Toggle the **Active** alert setting. The **URL** and **Authorization Key** for the webhook
       configuration are available in the **View credentials** tab after you save the integration.
       You must also input the URL and Authorization Key in your external service.
-   1. _(Optional)_ To map fields from your monitoring tool's alert to GitLab fields, enter a sample
+   1. Optional. To map fields from your monitoring tool's alert to GitLab fields, enter a sample
       payload and click **Parse payload for custom mapping**. Valid JSON is required. If you update
       a sample payload, you must also remap the fields.
 
-   1. _(Optional)_ If you provided a valid sample payload, select each value in
+   1. Optional. If you provided a valid sample payload, select each value in
       **Payload alert key** to [map to a **GitLab alert key**](#map-fields-in-custom-alerts).
    1. To save your integration, click **Save Integration**. If desired, you can send a test alert
       from your integration's **Send test alert** tab after the integration is created.

doc/topics/autodevops/multiple_clusters_auto_devops.md

@@ -27,7 +27,7 @@ The following table is an example of how to configure the three different cluste
 | Cluster name | Cluster environment scope | `KUBE_INGRESS_BASE_DOMAIN` variable value | Variable environment scope | Notes |
 |--------------|---------------------------|-------------------------------------------|----------------------------|---|
 | review       | `review/*`                | `review.example.com`                      | `review/*`                 | The review cluster which runs all [Review Apps](../../ci/review_apps/index.md). `*` is a wildcard, used by every environment name starting with `review/`. |
-| staging      | `staging`                 | `staging.example.com`                     | `staging`                  | (Optional) The staging cluster which runs the deployments of the staging environments. You must [enable it first](customize.md#deploy-policy-for-staging-and-production-environments). |
+| staging      | `staging`                 | `staging.example.com`                     | `staging`                  | Optional. The staging cluster that runs the deployments of the staging environments. You must [enable it first](customize.md#deploy-policy-for-staging-and-production-environments). |
 | production   | `production`              | `example.com`                             | `production`               | The production cluster which runs the production environment deployments. You can use [incremental rollouts](customize.md#incremental-rollout-to-production). |
 
 To add a different cluster for each environment:

doc/user/group/index.md

@@ -321,7 +321,7 @@ To share a group after enabling this feature:
 1. Go to your group's page.
 1. On the left sidebar, go to **Group information > Members**, and then select **Invite a group**.
 1. Select a group, and select a **Max role**.
-1. (Optional) Select an **Access expiration date**.
+1. Optional. Select an **Access expiration date**.
 1. Select **Invite**.
 
 ## Manage group memberships via LDAP **(PREMIUM SELF)**

doc/user/project/integrations/asana.md

@@ -37,7 +37,7 @@ Complete these steps in GitLab:
 1. Select **Asana**.
 1. Ensure that the **Active** toggle is enabled.
 1. Paste the token you generated in Asana.
-1. (Optional) To restrict this setting to specific branches, list them in the **Restrict to branch**
+1. Optional. To restrict this setting to specific branches, list them in the **Restrict to branch**
    field, separated with commas.
 1. Select **Save changes** or optionally select **Test settings**.
 

doc/user/project/integrations/hangouts_chat.md

@@ -32,7 +32,7 @@ Select a room and create a webhook:
 1. Enter the room where you want to receive notifications from GitLab.
 1. Open the room dropdown menu on the top-left and select **Manage webhooks**.
 1. Enter the name for your webhook, for example "GitLab integration".
-1. (Optional) Add an avatar for your bot.
+1. Optional. Add an avatar for your bot.
 1. Select **Save**.
 1. Copy the webhook URL.
 
@@ -46,7 +46,7 @@ Enable the Google Chat integration in GitLab:
 1. Scroll down to the end of the page where you find a **Webhook** field.
 1. Enter the webhook URL you copied from Google Chat.
 1. Select the events you want to be notified about in your Google Chat room.
-1. (Optional) Select **Test settings** to verify the connection.
+1. Optional. Select **Test settings** to verify the connection.
 1. Select **Save changes**.
 
 To test the integration, make a change based on the events you selected and

doc/user/project/integrations/mattermost.md

@@ -50,12 +50,12 @@ Then fill in the integration configuration:
 
 - **Webhook**: The incoming webhook URL on Mattermost, similar to
   `http://mattermost.example/hooks/5xo…`.
-- **Username**: (Optional) The username shown in messages sent to Mattermost.
+- **Username**: Optional. The username shown in messages sent to Mattermost.
   To change the bot's username, provide a value.
 - **Notify only broken pipelines**: If you enable the **Pipeline** event, and you want
   notifications about failed pipelines only.
 - **Branches for which notifications are to be sent**: The branches to send notifications for.
-- **Labels to be notified**: (Optional) Labels required for the issue or merge request
+- **Labels to be notified**: Optional. Labels required for the issue or merge request
   to trigger a notification. Leave blank to notify for all issues and merge requests.
 - **Labels to be notified behavior**: When you use the **Labels to be notified** filter,
   messages are sent when an issue or merge request contains _any_ of the labels specified

doc/user/project/integrations/pivotal_tracker.md

@@ -42,6 +42,6 @@ Complete these steps in GitLab:
 1. Select **Pivotal Tracker**.
 1. Ensure that the **Active** toggle is enabled.
 1. Paste the token you generated in Pivotal Tracker.
-1. (Optional) To restrict this setting to specific branches, list them in the **Restrict to branch**
+1. Optional. To restrict this setting to specific branches, list them in the **Restrict to branch**
    field, separated with commas.
 1. Select **Save changes** or optionally select **Test settings**.

doc/user/project/integrations/slack.md

@@ -31,7 +31,7 @@ to control GitLab from Slack. Slash commands are configured separately.
    [Triggers for Slack notifications](#triggers-for-slack-notifications).
    By default, messages are sent to the channel you configured during
    [Slack configuration](#configure-slack).
-1. (Optional) To send messages to a different channel, multiple channels, or as
+1. Optional. To send messages to a different channel, multiple channels, or as
    a direct message:
    - *To send messages to channels,* enter the Slack channel names, separated by
      commas.
@@ -42,7 +42,7 @@ to control GitLab from Slack. Slash commands are configured separately.
 
 1. In **Webhook**, enter the webhook URL you copied in the
    [Slack configuration](#configure-slack) step.
-1. (Optional) In **Username**, enter the username of the Slack bot that sends
+1. Optional. In **Username**, enter the username of the Slack bot that sends
    the notifications.
 1. Select the **Notify only broken pipelines** checkbox to notify only on failures.
 1. In the **Branches for which notifications are to be sent** dropdown, select which types of branches

doc/user/project/labels.md

@@ -72,9 +72,9 @@ To create a new project label:
 1. Select the **New label** button.
 1. In the **Title** field, enter a short, descriptive name for the label. You
    can also use this field to create [scoped, mutually exclusive labels](#scoped-labels).
-1. (Optional) In the **Description** field, you can enter additional
+1. Optional. In the **Description** field, you can enter additional
    information about how and when to use this label.
-1. (Optional) Select a background color for the label by selecting one of the
+1. Optional. Select a background color for the label by selecting one of the
    available colors, or by entering a hex color value in the **Background color**
    field.
 1. Select **Create label**.
@@ -86,7 +86,7 @@ label section of the right sidebar of an issue or a merge request:
 1. Click **Create project label**.
    - Fill in the name field. Note that you can't specify a description if creating a label
      this way. You can add a description later by editing the label (see below).
-   - (Optional) Select a color by clicking on the available colors, or input a hex
+   - Optional. Select a color by clicking on the available colors, or input a hex
      color value for a specific color.
 1. Click **Create**.
 

doc/user/project/merge_requests/approvals/rules.md

@@ -63,7 +63,7 @@ To edit a merge request approval rule:
 
 1. Go to your project and select **Settings > General**.
 1. Expand **Merge request (MR) approvals**, and then select **Edit**.
-1. (Optional) Change the **Rule name**.
+1. Optional. Change the **Rule name**.
 1. Set the number of required approvals in **Approvals required**. The minimum value is `0`.
 1. Add or remove eligible approvers, as needed:
    - *To add users or groups as approvers,* search for users or groups that are

doc/user/project/merge_requests/cherry_pick_changes.md

@@ -76,7 +76,7 @@ merge request is from a fork:
 1. Click on the **Options** dropdown and select **Cherry-pick** to show the cherry-pick modal.
 1. In **Pick into project** and **Pick into branch**, select the destination project and branch:
    ![Cherry-pick commit](img/cherry_pick_into_project_v13_11.png)
-1. (Optional) Select **Start a new merge request** if you're ready to create a merge request.
+1. Optional. Select **Start a new merge request** if you're ready to create a merge request.
 1. Click **Cherry-pick**.
 
 ## Related topics

doc/user/project/merge_requests/reviews/index.md

@@ -43,7 +43,7 @@ To start your review:
    - **Add to review**: Keep this comment private and add to the current review.
      These review comments are marked **Pending** and are visible only to you.
    - **Add comment now**: Submits the specific comment as a regular comment instead of as part of the review.
-1. (Optional) You can use [quick actions](../../quick_actions.md) inside review comments.
+1. Optional. You can use [quick actions](../../quick_actions.md) inside review comments.
    The comment shows the actions to perform after publication, but does not perform them
    until you submit your review.
 1. When your review is complete, you can [submit the review](#submit-a-review). Your comments

doc/user/project/repository/forking_workflow.md

@@ -101,7 +101,7 @@ To use it, follow the instructions at [Creating a fork](#creating-a-fork) and pr
 - The project name.
 - The project URL.
 - The project slug.
-- *(Optional)* The project description.
+- Optional. The project description.
 - The visibility level for your fork.
 
 ### Enable or disable the fork project form **(FREE SELF)**

doc/user/project/working_with_projects.md

@@ -194,7 +194,7 @@ To push a new project:
    remote: The private project namespace/myproject was created.
    ```
 
-1. (Optional) To configure the remote, alter the command
+1. Optional. To configure the remote, alter the command
    `git remote add origin https://gitlab.example.com/namespace/myproject.git`
    to match your namespace and project names.