Commit d3f9bb78 authored by ngaskill's avatar ngaskill

Correcting menu navigation characters

parent 6bc0f1f7
......@@ -68,7 +68,7 @@ You can only register a shared Runner if you are an admin of the GitLab instance
Shared Runners are enabled by default as of GitLab 8.2, but can be disabled
with the **Disable shared Runners** button which is present under each project's
**Settings CI/CD** page. Previous versions of GitLab defaulted shared
**Settings > CI/CD** page. Previous versions of GitLab defaulted shared
Runners to disabled.
## Registering a specific Runner
......@@ -402,7 +402,7 @@ different places.
To view the IP address of a shared Runner you must have admin access to
the GitLab instance. To determine this:
1. Visit **Admin Area ➔ Overview ➔ Runners**
1. Visit **Admin Area > Overview > Runners**
1. Look for the Runner in the table and you should see a column for "IP Address"
![shared Runner IP address](img/shared_runner_ip_address.png)
......@@ -411,7 +411,7 @@ the GitLab instance. To determine this:
You can find the IP address of a Runner for a specific project by:
1. Visit your project's **Settings CI/CD**
1. Visit your project's **Settings > CI/CD**
1. Find the Runner and click on it's ID which links you to the details page
1. On the details page you should see a row for "IP Address"
......
......@@ -141,7 +141,7 @@ This check is being exempt from Rack Attack.
> Access token has been deprecated in GitLab 9.4 in favor of [IP whitelist](#ip-whitelist).
An access token needs to be provided while accessing the probe endpoints. The current
accepted token can be found under the **Admin Area ➔ Monitoring ➔ Health check**
accepted token can be found under the **Admin Area > Monitoring > Health check**
(`admin/health_check`) page of your GitLab instance.
![access token](img/health_check_token.png)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment