This is an automated email from the ASF dual-hosted git repository.

pifta pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone.git


The following commit(s) were added to refs/heads/master by this push:
     new 6c7af5c0b7 HDDS-10261. Fix typos in Architecture Documentation (#6141)
6c7af5c0b7 is described below

commit 6c7af5c0b797b6d12a730e35304bc764dd1051f0
Author: Sarveksha Yeshavantha Raju 
<[email protected]>
AuthorDate: Thu Feb 1 15:02:58 2024 +0530

    HDDS-10261. Fix typos in Architecture Documentation (#6141)
---
 hadoop-hdds/docs/content/concept/Datanodes.md               | 2 +-
 hadoop-hdds/docs/content/concept/OzoneManager.md            | 2 +-
 hadoop-hdds/docs/content/concept/Recon.md                   | 2 +-
 hadoop-hdds/docs/content/concept/StorageContainerManager.md | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/hadoop-hdds/docs/content/concept/Datanodes.md 
b/hadoop-hdds/docs/content/concept/Datanodes.md
index 1149eba2b0..47c09a798f 100644
--- a/hadoop-hdds/docs/content/concept/Datanodes.md
+++ b/hadoop-hdds/docs/content/concept/Datanodes.md
@@ -48,7 +48,7 @@ the key to the Ozone Manager. Ozone manager returns the list 
of Ozone blocks
 that make up that key.
 
 An Ozone block contains the container ID and a local ID. The figure below
-shows the logical layout out of Ozone block.
+shows the logical layout of the Ozone block.
 
 ![Ozone Block](OzoneBlock.png)
 
diff --git a/hadoop-hdds/docs/content/concept/OzoneManager.md 
b/hadoop-hdds/docs/content/concept/OzoneManager.md
index 31f6a42810..f58a4cd8f4 100644
--- a/hadoop-hdds/docs/content/concept/OzoneManager.md
+++ b/hadoop-hdds/docs/content/concept/OzoneManager.md
@@ -31,7 +31,7 @@ Ozone Manager (OM) is the namespace manager for Ozone.
 This means that when you want to write some data, you ask Ozone
 Manager for a block and Ozone Manager gives you a block and remembers that
 information. When you want to read that file back, you need to find the
-address of the block and Ozone Manager returns it you.
+address of the block and the Ozone Manager returns it to you.
 
 Ozone Manager also allows users to organize keys under a volume and bucket.
 Volumes and buckets are part of the namespace and managed by Ozone Manager.
diff --git a/hadoop-hdds/docs/content/concept/Recon.md 
b/hadoop-hdds/docs/content/concept/Recon.md
index 235d6c314f..608a37c39b 100644
--- a/hadoop-hdds/docs/content/concept/Recon.md
+++ b/hadoop-hdds/docs/content/concept/Recon.md
@@ -153,7 +153,7 @@ ozone.recon.db.dir | none | Directory where the Recon 
Server stores its metadata
 ozone.recon.om.db.dir | none | Directory where the Recon Server stores its OM 
snapshot DB.
 ozone.recon.om.snapshot<br>.task.interval.delay | 10m | Interval in MINUTES by 
Recon to request OM DB Snapshot / delta updates.
 ozone.recon.task<br>.missingcontainer.interval | 300s | Time interval of the 
periodic check for Unhealthy Containers in the cluster.
-ozone.recon.task<br>.safemode.wait.threshold | 300s | Max time for Recon to 
wait before it exit out of safe or warmup mode.
+ozone.recon.task<br>.safemode.wait.threshold | 300s | Max time for Recon to 
wait before it exits out of safe or warmup mode.
 ozone.recon.sql.db.jooq.dialect | DERBY | Please refer to [SQL 
Dialect](https://www.jooq.org/javadoc/latest/org.jooq/org/jooq/SQLDialect.html) 
to specify a different dialect.
 ozone.recon.sql.db.jdbc.url | 
jdbc:derby:${ozone.recon.db.dir}<br>/ozone_recon_derby.db | Recon SQL database 
jdbc url.
 ozone.recon.sql.db.username | none | Recon SQL database username.
diff --git a/hadoop-hdds/docs/content/concept/StorageContainerManager.md 
b/hadoop-hdds/docs/content/concept/StorageContainerManager.md
index 8922f89bc5..860e69a77d 100644
--- a/hadoop-hdds/docs/content/concept/StorageContainerManager.md
+++ b/hadoop-hdds/docs/content/concept/StorageContainerManager.md
@@ -43,7 +43,7 @@ read and write these blocks directly.
 
  2. SCM keeps track of all the block
 replicas. If there is a loss of data node or a disk, SCM
-detects it and instructs data nodes make copies of the
+detects it and instructs data nodes to make copies of the
 missing blocks to ensure high availability.
 
  3. **SCM's Certificate Authority** is in


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to