harmacist/healthchecks
1
0
Fork 0
forked from GithubBackups/healthchecks
Code Issues Pull Requests Projects Releases Wiki Activity

Rename "Signalling Failures" -> "Signaling Failures"

Browse Source
This commit is contained in:
Pēteris Caune 2020-12-28 14:12:07 +02:00
parent 70519fcd89
commit 02b5ec3657
No known key found for this signature in database
GPG Key ID: E28D7679E9A9EDE2
6 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
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> 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 <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 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 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": 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> SITE_NAME will ignore all incoming pings until you explicitly <em>resume</em> the check.</li>

2
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. 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 * **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 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 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": 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. SITE_NAME will ignore all incoming pings until you explicitly *resume* the check.

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

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

2
templates/front/base_docs.html
View File

@ -33,7 +33,7 @@
<li class="nav-header">Guides</li> <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="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="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="attaching_logs" title="Attaching logs" %}
{% include "front/docs_nav_item.html" with slug="cloning_checks" title="Cloning checks" %} {% include "front/docs_nav_item.html" with slug="cloning_checks" title="Cloning checks" %}

2
templates/front/details.html
View File

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