This is an automated email from the ASF dual-hosted git repository.
jialiang pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/ambari.git
The following commit(s) were added to refs/heads/trunk by this push:
new 2c2917aaeb AMBARI-26104: [fix][doc] Correcting spelling mistakes #3752
2c2917aaeb is described below
commit 2c2917aaeb7781b6eb7b6443a4a02d6d2d964ebd
Author: wangda <[email protected]>
AuthorDate: Wed Jul 31 14:31:49 2024 +0800
AMBARI-26104: [fix][doc] Correcting spelling mistakes #3752
Signed-off-by: zhangwd3 <[email protected]>
Co-authored-by: zhangwd3 <[email protected]>
---
ambari-server/docs/api/v1/alert-dispatching.md | 2 +-
ambari-server/docs/api/v1/index.md | 2 +-
ambari-server/docs/configuration/index.md | 2 +-
ambari-views/docs/index.md | 2 +-
ambari-views/examples/restricted-view/docs/index.md | 2 +-
dev-support/docker/centos7/README.md | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/ambari-server/docs/api/v1/alert-dispatching.md
b/ambari-server/docs/api/v1/alert-dispatching.md
index 8326e5ee05..90a9499e50 100644
--- a/ambari-server/docs/api/v1/alert-dispatching.md
+++ b/ambari-server/docs/api/v1/alert-dispatching.md
@@ -37,7 +37,7 @@ Any number of targets can be associated with an alert group
(a grouping of defin
There is also a `global` alert target which can be used as a way to produce
notifications for any alert defined in Ambari. These `global` targets are never
associated with any groups; they apply to all groups and all definitions.
##### Notices
-Once an alert has changed state, Ambari will determine if there are any
targets that should receive a notification of the state change. These
notifications, or notices, are created with an initial status of `PENDING` and
will transition either to `DELIVERED` or `FAILED` once the proper dispatcher
has attemped to process the notice. Dispatchers can attempt to aggregate any
`PENDING` notices into a single outbound notification.
+Once an alert has changed state, Ambari will determine if there are any
targets that should receive a notification of the state change. These
notifications, or notices, are created with an initial status of `PENDING` and
will transition either to `DELIVERED` or `FAILED` once the proper dispatcher
has attempted to process the notice. Dispatchers can attempt to aggregate any
`PENDING` notices into a single outbound notification.
### API Summary
diff --git a/ambari-server/docs/api/v1/index.md
b/ambari-server/docs/api/v1/index.md
index e8abcb633b..4bdbcff23d 100644
--- a/ambari-server/docs/api/v1/index.md
+++ b/ambari-server/docs/api/v1/index.md
@@ -176,7 +176,7 @@ Delete the cluster named 'c1'.
### Asynchronous Response
-The managment APIs can return a response code of 202 which indicates that the
request has been accepted. The body of the response contains the ID and href
of the request resource that was created to carry out the instruction.
+The management APIs can return a response code of 202 which indicates that the
request has been accepted. The body of the response contains the ID and href
of the request resource that was created to carry out the instruction.
202 Accepted
{
diff --git a/ambari-server/docs/configuration/index.md
b/ambari-server/docs/configuration/index.md
index 7a1b7184f6..01c61d8caa 100644
--- a/ambari-server/docs/configuration/index.md
+++ b/ambari-server/docs/configuration/index.md
@@ -234,7 +234,7 @@ The following are the properties which can be used to
configure Ambari.
| server.metrics.retrieval-service.thread.priority | The priority of threads
used by the service which retrieves JMX and REST metrics directly from their
respective endpoints. |`5` |
| server.metrics.retrieval-service.threadpool.size.core | The core number of
threads used to retrieve JMX and REST metrics directly from their respective
endpoints. |`4` |
| server.metrics.retrieval-service.threadpool.size.max | The maximum number of
threads used to retrieve JMX and REST metrics directly from their respective
endpoints. |`8` |
-| server.metrics.retrieval-service.threadpool.worker.size | The number of
queued requests allowed for JMX and REST metrics before discarding old requests
which have not been fullfilled. |`80` |
+| server.metrics.retrieval-service.threadpool.worker.size | The number of
queued requests allowed for JMX and REST metrics before discarding old requests
which have not been fulfilled. |`80` |
| server.operations.retry-attempts | The number of retry attempts for failed
API and blueprint operations. |`0` |
| server.os_family | The operating system family for all hosts in the cluster.
This is used when bootstrapping agents and when enabling Kerberos.<br/><br/>The
following are examples of valid values:<ul><li>`redhat`<li>`ubuntu`</ul> | |
| server.os_type | The operating system version for all hosts in the cluster.
This is used when bootstrapping agents and when enabling Kerberos.<br/><br/>The
following are examples of valid values:<ul><li>`6`<li>`7`</ul> | |
diff --git a/ambari-views/docs/index.md b/ambari-views/docs/index.md
index 302d6a79d9..407fc82a44 100644
--- a/ambari-views/docs/index.md
+++ b/ambari-views/docs/index.md
@@ -1085,7 +1085,7 @@ Because the resource is managed through the Ambari API
framework, it may be quer
#####Grant view privileges
-To grant privileges to access the restricted resource we can create a
privilege sub-resource for the view instance. The following API will grant
RESTICTED permission to the user 'bob' for the view instance 'INSTANCE_1' of
the 'RESTRICTED' view.
+To grant privileges to access the restricted resource we can create a
privilege sub-resource for the view instance. The following API will grant
RESTRICTED permission to the user 'bob' for the view instance 'INSTANCE_1' of
the 'RESTRICTED' view.
POST
http://<server>/api/v1/views/RESTRICTED/versions/1.0.0/instances/INSTANCE_1
diff --git a/ambari-views/examples/restricted-view/docs/index.md
b/ambari-views/examples/restricted-view/docs/index.md
index 78aced4523..14b469cb5f 100644
--- a/ambari-views/examples/restricted-view/docs/index.md
+++ b/ambari-views/examples/restricted-view/docs/index.md
@@ -231,7 +231,7 @@ If we try to access the view's restricted resource through
the resource's href i
401 Unauthorized
-To grant privileges to access the restricted resource we can create a
privilege sub-resource for the view instance. The following API will grant
RESTICTED permission to the user 'bob' for the view instance 'INSTANCE_1' of
the 'RESTRICTED' view.
+To grant privileges to access the restricted resource we can create a
privilege sub-resource for the view instance. The following API will grant
RESTRICTED permission to the user 'bob' for the view instance 'INSTANCE_1' of
the 'RESTRICTED' view.
POST
http://<server>/api/v1/views/RESTRICTED/versions/1.0.0/instances/INSTANCE_1
diff --git a/dev-support/docker/centos7/README.md
b/dev-support/docker/centos7/README.md
index c976c0b4c4..494726b2e9 100644
--- a/dev-support/docker/centos7/README.md
+++ b/dev-support/docker/centos7/README.md
@@ -31,7 +31,7 @@ git clone https://github.com/apache/ambari.git
cd ambari/dev-support/docker/centos7/
```
### **Step 4**: Build develop basic image
-Run the setup command, you will get `ambari/develop:trunk-centos-7` image. It
has the enviroment needed to compile Ambari and run servers such as Ambari
Server, Ambari Agent, Mysql, etc.
+Run the setup command, you will get `ambari/develop:trunk-centos-7` image. It
has the environment needed to compile Ambari and run servers such as Ambari
Server, Ambari Agent, Mysql, etc.
**RHEL (CentOS 7) :**
```shell
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
