docs/*: Fix misspell issues

See, $ find . -type f | xargs misspell -locale US | grep -vi -e vendor -e node_modules -e devenv -e unknwon | grep docs
2025-02-25 18:55:37 -06:00 · 2018-11-28 20:33:41 +01:00
parent 9c1b4793a6
commit 5d60d323e2
9 changed files with 51 additions and 51 deletions
--- a/docs/sources/administration/provisioning.md
+++ b/docs/sources/administration/provisioning.md
@@ -230,4 +230,4 @@ By default Grafana will delete dashboards in the database if the file is removed
 > **Note.** Provisioning allows you to overwrite existing dashboards
 > which leads to problems if you re-use settings that are supposed to be unique.
 > Be careful not to re-use the same `title` multiple times within a folder
-> or `uid` within the same installation as this will cause weird behaviours.
+> or `uid` within the same installation as this will cause weird behaviors.
--- a/docs/sources/alerting/notifications.md
+++ b/docs/sources/alerting/notifications.md
@@ -136,7 +136,7 @@ In DingTalk PC Client:

 2. Click "Robot Manage" item in the pop menu, there will be a new panel call "Robot Manage".

-3. In the  "Robot Manage" panel, select "customised: customised robot with Webhook".
+3. In the  "Robot Manage" panel, select "customized: customized robot with Webhook".

 4. In the next new panel named "robot detail", click "Add" button.

--- a/docs/sources/auth/ldap.md
+++ b/docs/sources/auth/ldap.md
@@ -163,9 +163,9 @@ org_role = "Viewer"
 Setting | Required | Description | Default
 ------------ | ------------ | ------------- | -------------
 `group_dn` | Yes | LDAP distinguished name (DN) of LDAP group. If you want to match all (or no LDAP groups) then you can use wildcard (`"*"`) |
-`org_role` | Yes | Assign users of `group_dn` the organisation role `"Admin"`, `"Editor"` or `"Viewer"` |
+`org_role` | Yes | Assign users of `group_dn` the organization role `"Admin"`, `"Editor"` or `"Viewer"` |
 `org_id` | No | The Grafana organization database id. Setting this allows for multiple group_dn's to be assigned to the same `org_role` provided the `org_id` differs | `1` (default org id)
-`grafana_admin` | No | When `true` makes user of `group_dn` Grafana server admin. A Grafana server admin has admin access over all organisations and users. Available in Grafana v5.3 and above | `false`
+`grafana_admin` | No | When `true` makes user of `group_dn` Grafana server admin. A Grafana server admin has admin access over all organizations and users. Available in Grafana v5.3 and above | `false`

 ### Nested/recursive group membership

--- a/docs/sources/contribute/cla.md
+++ b/docs/sources/contribute/cla.md
@@ -1,6 +1,6 @@
 +++
-title = "Contributor Licence Agreement (CLA)"
-description = "Contributor Licence Agreement (CLA)"
+title = "Contributor License Agreement (CLA)"
+description = "Contributor License Agreement (CLA)"
 type = "docs"
 aliases = ["/project/cla", "docs/contributing/cla.html"]
 [menu.docs]
--- a/docs/sources/enterprise/index.md
+++ b/docs/sources/enterprise/index.md
@@ -31,7 +31,7 @@ Datasource permissions allow you to restrict query access to only specific Teams

 ### Premium Plugins

-With a Grafana Enterprise licence you will get access to premium plugins, including:
+With a Grafana Enterprise license you will get access to premium plugins, including:

 * [Splunk](https://grafana.com/plugins/grafana-splunk-datasource)
 * [AppDynamics](https://grafana.com/plugins/dlopes7-appdynamics-datasource)
--- a/docs/sources/guides/whats-new-in-v4.md
+++ b/docs/sources/guides/whats-new-in-v4.md
@@ -134,7 +134,7 @@ continue work on a `build mode` for a future release.
 The new row menu automatically slides out when you mouse over the edge of the row. You no longer need
 to hover over the small green icon and then click it to expand the row menu.

-There are some minor improvements to drag and drop behaviour. Now when dragging a panel from one row
+There are some minor improvements to drag and drop behavior. Now when dragging a panel from one row
 to another you will insert the panel and Grafana will automatically make room for it.
 When you drag a panel within a row you will simply reorder the panels.

--- a/docs/sources/http_api/index.md
+++ b/docs/sources/http_api/index.md
@@ -26,7 +26,7 @@ dashboards, creating users and updating data sources.
 * [Folder Permissions API]({{< relref "http_api/folder_permissions.md" >}})
 * [Folder/dashboard search API]({{< relref "/http_api/folder_dashboard_search.md" >}})
 * [Data Source API]({{< relref "http_api/data_source.md" >}})
-* [Organisation API]({{< relref "http_api/org.md" >}})
+* [Organization API]({{< relref "http_api/org.md" >}})
 * [Snapshot API]({{< relref "http_api/snapshot.md" >}})
 * [Annotations API]({{< relref "http_api/annotations.md" >}})
 * [Alerting API]({{< relref "http_api/alerting.md" >}})
--- a/docs/sources/http_api/org.md
+++ b/docs/sources/http_api/org.md
@@ -1,24 +1,24 @@
 +++
-title = "Organisation HTTP API "
-description = "Grafana Organisation HTTP API"
-keywords = ["grafana", "http", "documentation", "api", "organisation"]
-aliases = ["/http_api/organisation/"]
+title = "Organization HTTP API "
+description = "Grafana Organization HTTP API"
+keywords = ["grafana", "http", "documentation", "api", "organization"]
+aliases = ["/http_api/organization/"]
 type = "docs"
 [menu.docs]
-name = "Organisation"
+name = "Organization"
 parent = "http_api"
 +++


-# Organisation API
+# Organization API

-The Organisation HTTP API is divided in two resources, `/api/org` (current organisation)
-and `/api/orgs` (admin organisations). One big difference between these are that
-the admin of all organisations API only works with basic authentication, see [Admin Organisations API](#admin-organisations-api) for more information.
+The Organization HTTP API is divided in two resources, `/api/org` (current organization)
+and `/api/orgs` (admin organizations). One big difference between these are that
+the admin of all organizations API only works with basic authentication, see [Admin Organizations API](#admin-organizations-api) for more information.

-## Current Organisation API
+## Current Organization API

-### Get current Organisation
+### Get current Organization

 `GET /api/org/`

@@ -43,7 +43,7 @@ Content-Type: application/json

 `GET /api/org/users`

-**Example Request**:
+**Example Request**:

 ```http
 GET /api/org/users HTTP/1.1
@@ -99,7 +99,7 @@ Content-Type: application/json

 ```http
 HTTP/1.1 200
-Content-Type: application/json
+Content-Type: application/json

 ```

@@ -121,7 +121,7 @@ Content-Type: application/json

 ```http
 HTTP/1.1 200
-Content-Type: application/json
+Content-Type: application/json

 ```

@@ -147,11 +147,11 @@ Content-Type: application/json
 HTTP/1.1 200
 Content-Type: application/json

-```
+```

 ## Admin Organizations API

-The Admin Organisations HTTP API does not currently work with an API Token. API Tokens are currently
+The Admin Organizations HTTP API does not currently work with an API Token. API Tokens are currently
 only linked to an organization and an organization role. They cannot be given the permission of server
 admin, only users can be given that permission. So in order to use these API calls you will have to
 use Basic Auth and the Grafana user must have the Grafana Admin permission (The default admin user
@@ -176,19 +176,19 @@ Content-Type: application/json
 ```http
 HTTP/1.1 200
 Content-Type: application/json
-
+
 ```
-### Get Organisation by Name
+### Get Organization by Name

 `GET /api/orgs/name/:orgName`

 Only works with Basic Authentication (username and password), see [introduction](#admin-organizations-api).

-**Example Request**:
+**Example Request**:

 ```http
 GET /api/orgs/name/Main%20Org%2E HTTP/1.1
-Accept: application/json
+Accept: application/json
 Content-Type: application/json
 ```

@@ -217,11 +217,11 @@ Content-Type: application/json
 Note: The api will work in the following two ways
 1) Need to set GF_USERS_ALLOW_ORG_CREATE=true
 2) Set the config users.allow_org_create to true in ini file
-
+
 **Example Response**:

 ```http
-HTTP/1.1 200
+HTTP/1.1 200
 Content-Type: application/json

 ```
@@ -251,11 +251,11 @@ Content-Type: application/json
 ```

 ### Update Organization
-
+
 `PUT /api/orgs/:orgId`

 Update Organization, fields *Address 1*, *Address 2*, *City* are not implemented yet.
-Only works with Basic Authentication (username and password), see [introduction](#admin-organisations-api).
+Only works with Basic Authentication (username and password), see [introduction](#admin-organizations-api).

 **Example Request**:

@@ -284,11 +284,11 @@ Content-Type: application/json

 ```http
 DELETE /api/orgs/1 HTTP/1.1
-Accept: application/json
+Accept: application/json
 ```

 **Example Response**:
-
+
 ```http
 HTTP/1.1 200
 Content-Type: application/json
@@ -314,12 +314,12 @@ Content-Type: application/json

 **Example Response**:

-```http
+```http
 HTTP/1.1 200
 Content-Type: application/json
 [
-```
-
+```
+
 ### Add User in Organization

 `POST /api/orgs/:orgId/users`
@@ -342,11 +342,11 @@ Content-Type: application/json
 Content-Type: application/json

 ```
-
+
 ### Update Users in Organization

 `PATCH /api/orgs/:orgId/users/:userId`
-
+
 Only works with Basic Authentication (username and password), see [introduction](#admin-organizations-api).

 **Example Request**:
@@ -364,11 +364,11 @@ Content-Type: application/json
 HTTP/1.1 200
 Content-Type: application/json

-```
+```

 ### Delete User in Organization

-`DELETE /api/orgs/:orgId/users/:userId`
+`DELETE /api/orgs/:orgId/users/:userId`

 Only works with Basic Authentication (username and password), see [introduction](#admin-organizations-api).

@@ -397,11 +397,11 @@ Content-Type: application/json
 ]
 ```

-### Add User in Organisation
+### Add User in Organization

 `POST /api/orgs/:orgId/users`

-Only works with Basic Authentication (username and password), see [introduction](#admin-organisations-api).
+Only works with Basic Authentication (username and password), see [introduction](#admin-organizations-api).

 **Example Request**:

@@ -425,11 +425,11 @@ Content-Type: application/json
 {"message":"User added to organization"}
 ```

-### Update Users in Organisation
+### Update Users in Organization

 `PATCH /api/orgs/:orgId/users/:userId`

-Only works with Basic Authentication (username and password), see [introduction](#admin-organisations-api).
+Only works with Basic Authentication (username and password), see [introduction](#admin-organizations-api).

 **Example Request**:

@@ -452,11 +452,11 @@ Content-Type: application/json
 {"message":"Organization user updated"}
 ```

-### Delete User in Organisation
+### Delete User in Organization

 `DELETE /api/orgs/:orgId/users/:userId`

-Only works with Basic Authentication (username and password), see [introduction](#admin-organisations-api).
+Only works with Basic Authentication (username and password), see [introduction](#admin-organizations-api).

 **Example Request**:

--- a/docs/sources/http_api/user.md
+++ b/docs/sources/http_api/user.md
@@ -196,7 +196,7 @@ Content-Type: application/json
 GET /api/user HTTP/1.1
 Accept: application/json
 Content-Type: application/json
-Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
+Authorization: Bearer eyJrIjoiT0tTcG1pUlY2RnVKZTFVaDFsNFZXdE9ZWmNrMkZYbk
 ```

 **Example Response**:
@@ -367,11 +367,11 @@ Content-Type: application/json

 ```

-## Organisations of the actual User
+## Organizations of the actual User

 `GET /api/user/orgs`

-Return a list of all organisations of the current user.
+Return a list of all organizations of the current user.

 **Example Request**: