forked from GithubBackups/healthchecks
Fix typos with codespell
This commit is contained in:
parent
f7acaa57af
commit
38382d662d
@ -196,7 +196,7 @@ DATABASES = {
|
||||
|
||||
## Accessing Administration Panel
|
||||
|
||||
healthchecks comes with Django's administation panel where you can manually
|
||||
healthchecks comes with Django's administration panel where you can manually
|
||||
view and modify user accounts, projects, checks, integrations etc. To access it,
|
||||
|
||||
* if you haven't already, create a superuser account: `./manage.py createsuperuser`
|
||||
|
@ -42,7 +42,7 @@ class Transport(object):
|
||||
def is_noop(self, check):
|
||||
""" Return True if transport will ignore check's current status.
|
||||
|
||||
This method is overriden in Webhook subclass where the user can
|
||||
This method is overridden in Webhook subclass where the user can
|
||||
configure webhook urls for "up" and "down" events, and both are
|
||||
optional.
|
||||
|
||||
|
@ -295,7 +295,7 @@ ignored and "schedule" will be used.</p>
|
||||
<dd>
|
||||
<p>string, optional, default value: "UTC".</p>
|
||||
<p>Server's timezone. This setting only has effect in combination with the
|
||||
"schedule" paremeter.</p>
|
||||
"schedule" parameter.</p>
|
||||
<p>Example:</p>
|
||||
<p><pre>{"tz": "Europe/Riga"}</pre></p>
|
||||
</dd>
|
||||
@ -423,7 +423,7 @@ ignored and "schedule" will be used.</p>
|
||||
<dd>
|
||||
<p>string, optional.</p>
|
||||
<p>Server's timezone. This setting only has effect in combination with the
|
||||
"schedule" paremeter.</p>
|
||||
"schedule" parameter.</p>
|
||||
<p>Example:</p>
|
||||
<p><pre>{"tz": "Europe/Riga"}</pre></p>
|
||||
</dd>
|
||||
|
@ -299,7 +299,7 @@ tz
|
||||
: string, optional, default value: "UTC".
|
||||
|
||||
Server's timezone. This setting only has effect in combination with the
|
||||
"schedule" paremeter.
|
||||
"schedule" parameter.
|
||||
|
||||
Example:
|
||||
|
||||
@ -453,7 +453,7 @@ tz
|
||||
: string, optional.
|
||||
|
||||
Server's timezone. This setting only has effect in combination with the
|
||||
"schedule" paremeter.
|
||||
"schedule" parameter.
|
||||
|
||||
Example:
|
||||
|
||||
|
@ -35,7 +35,7 @@ limit depends on the account's billing plan.</p>
|
||||
<p>Account's check limit is shared by all projects owned by your account.
|
||||
For example, consider a Business account with two projects,
|
||||
"Project A" and "Project B". If A has 70 checks, then B cannot have more than
|
||||
30 checks, in order to not exceed Bussiness account's total limit of 100.</p>
|
||||
30 checks, in order to not exceed business account's total limit of 100.</p>
|
||||
<p>However, only checks from your own projects count towards your account's
|
||||
quota. If you get invited to somebody else's project, that does not change
|
||||
the number of checks you can create in your own projects.</p>
|
||||
@ -47,4 +47,4 @@ projects, it only takes up a single "seat".</p>
|
||||
<h2>Projects and Monthly Reports</h2>
|
||||
<p>SITE_NAME sends monthly email reports at the
|
||||
start of each month. The monthly reports list a summary of checks from
|
||||
<strong>all projects you have access to</strong> (either as the owner or as a member).</p>
|
||||
<strong>all projects you have access to</strong> (either as the owner or as a member).</p>
|
||||
|
@ -45,7 +45,7 @@ limit depends on the account's billing plan.
|
||||
Account's check limit is shared by all projects owned by your account.
|
||||
For example, consider a Business account with two projects,
|
||||
"Project A" and "Project B". If A has 70 checks, then B cannot have more than
|
||||
30 checks, in order to not exceed Bussiness account's total limit of 100.
|
||||
30 checks, in order to not exceed business account's total limit of 100.
|
||||
|
||||
However, only checks from your own projects count towards your account's
|
||||
quota. If you get invited to somebody else's project, that does not change
|
||||
|
Loading…
x
Reference in New Issue
Block a user