Skip to content

Docs reformatting with :guilabel: #5161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Feb 12, 2019
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/advertising/ethical-advertising.rst
Original file line number Diff line number Diff line change
Expand Up @@ -160,7 +160,7 @@ Users can opt out of seeing paid advertisements on documentation pages:
Project owners can also opt out of paid advertisements for their projects.
You can change these options:

* Click on your :guilabel:`Project` page (`/projects/<slug>/`)
* Go to your **project** page (`/projects/<slug>/`)
* Go to :guilabel:`Admin` > :guilabel:`Advertising`
* Change your advertising settings

Expand Down
4 changes: 2 additions & 2 deletions docs/guides/build-notifications.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This makes sure you know when your builds have failed.
Take these steps to enable build notifications using email:

* Go to :guilabel:`Admin` > :guilabel:`Notifications` in your project.
* Fill in the **Email** field under the :guilabel:`New Email Notifications` heading
* Fill in the **Email** field under the **New Email Notifications** heading
* Submit the form

You should now get notified by email when your builds fail!
Expand All @@ -23,7 +23,7 @@ Read the Docs can also send webhooks when builds fail.
Take these steps to enable build notifications using a webhook:

* Go to :guilabel:`Admin` > :guilabel:`Notifications` in your project.
* Fill in the **URL** field under the :guilabel:`New Webhook Notifications` heading
* Fill in the **URL** field under the **New Webhook Notifications** heading
* Submit the form

The project name, slug and its details for the build that failed will be sent as POST request to your webhook URL:
Expand Down
10 changes: 5 additions & 5 deletions docs/webhooks.rst
Original file line number Diff line number Diff line change
Expand Up @@ -87,9 +87,9 @@ Using the generic API integration
---------------------------------

For repositories that are not hosted with a supported provider, we also offer a
generic API endpoint for triggering project builds. Similar to webhook
integrations, this integration has a specific URL, found on the project's
:guilabel:`Admin` > :guilabel:`Integrations` dashboard page on readthedocs.org.
generic API endpoint for triggering project builds. Similar to webhook integrations,
this integration has a specific URL, which can be found on the project's **Integrations** dashboard page.
(:guilabel:`Admin` > :guilabel:`Integrations`).

Token authentication is required to use the generic endpoint, you will find this
token on the integration details page. The token should be passed in as a
Expand All @@ -107,8 +107,8 @@ branches
Default: **latest**

token
The integration token. You'll find this value on the project's
:guilabel:`Admin` > :guilabel:`Integrations` dashboard page.
The integration token found on the project's **Integrations** dashboard page.
(:guilabel:`Admin` > :guilabel:`Integrations`)

For example, the cURL command to build the ``dev`` branch, using the token
``1234``, would be::
Expand Down