Browse Source

Rename "Signalling Failures" -> "Signaling Failures"

pull/468/head
Pēteris Caune 4 years ago
parent
commit
02b5ec3657
No known key found for this signature in database GPG Key ID: E28D7679E9A9EDE2
6 changed files with 4 additions and 4 deletions
  1. +1
    -1
      templates/docs/configuring_checks.html
  2. +1
    -1
      templates/docs/configuring_checks.md
  3. +0
    -0
      templates/docs/signaling_failures.html
  4. +0
    -0
      templates/docs/signaling_failures.md
  5. +1
    -1
      templates/front/base_docs.html
  6. +1
    -1
      templates/front/details.html

+ 1
- 1
templates/docs/configuring_checks.html View File

@ -62,7 +62,7 @@ For example, this is useful if your backup software sends an email after each ba
run with a different subject line depending on success or failure.</li>
<li><strong>Pinging a Paused Check</strong>. Normally, when you ping a paused check, it leaves the
paused state and goes into the "up" state (or the "down" state
in case of <a href="../signalling_failures/">a failure signal</a>).
in case of <a href="../signaling_failures/">a failure signal</a>).
You can change this behavior by selecting the "Ignore the ping, stay in
the paused state" option. With this option selected, the paused state becomes "sticky":
SITE_NAME will ignore all incoming pings until you explicitly <em>resume</em> the check.</li>

+ 1
- 1
templates/docs/configuring_checks.md View File

@ -74,7 +74,7 @@ For example, this is useful if your backup software sends an email after each ba
run with a different subject line depending on success or failure.
* **Pinging a Paused Check**. Normally, when you ping a paused check, it leaves the
paused state and goes into the "up" state (or the "down" state
in case of [a failure signal](../signalling_failures/)).
in case of [a failure signal](../signaling_failures/)).
You can change this behavior by selecting the "Ignore the ping, stay in
the paused state" option. With this option selected, the paused state becomes "sticky":
SITE_NAME will ignore all incoming pings until you explicitly *resume* the check.

templates/docs/signalling_failures.html → templates/docs/signaling_failures.html View File


templates/docs/signalling_failures.md → templates/docs/signaling_failures.md View File


+ 1
- 1
templates/front/base_docs.html View File

@ -33,7 +33,7 @@
<li class="nav-header">Guides</li>
{% include "front/docs_nav_item.html" with slug="monitoring_cron_jobs" title="Monitoring cron jobs" %}
{% include "front/docs_nav_item.html" with slug="signalling_failures" title="Signalling failures" %}
{% include "front/docs_nav_item.html" with slug="signaling_failures" title="Signaling failures" %}
{% include "front/docs_nav_item.html" with slug="measuring_script_run_time" title="Measuring script run time" %}
{% include "front/docs_nav_item.html" with slug="attaching_logs" title="Attaching logs" %}
{% include "front/docs_nav_item.html" with slug="cloning_checks" title="Cloning checks" %}


+ 1
- 1
templates/front/details.html View File

@ -87,7 +87,7 @@
<code>{{ check.email }}</code>
<p>You can also explicitly
<a href="{% url 'hc-serve-doc' 'signalling_failures' %}">
<a href="{% url 'hc-serve-doc' 'signaling_failures' %}">
signal a failure</a>
and
<a href="{% url 'hc-serve-doc' 'measuring_script_run_time' %}">


Loading…
Cancel
Save