address review comments
diff --git a/hadoop-hdds/docs/content/concept/OzoneManager.md b/hadoop-hdds/docs/content/concept/OzoneManager.md
index 06de7c7..f0711ed 100644
--- a/hadoop-hdds/docs/content/concept/OzoneManager.md
+++ b/hadoop-hdds/docs/content/concept/OzoneManager.md
@@ -24,7 +24,7 @@
limitations under the License.
-->
-
+
Ozone Manager (OM) is the namespace manager for Ozone.
@@ -141,4 +141,4 @@
----|-------------|--------
ozone.om.address | 0.0.0.0:9862 | RPC address of the OM. Required by the client.
ozone.om.http-address | 0.0.0.0:9874 | Default port of the HTTP server.
-ozone.metadata.dirs | none | Directory to store persisted data (RocksDB).
\ No newline at end of file
+ozone.metadata.dirs | none | Directory to store persisted data (RocksDB).
diff --git a/hadoop-hdds/docs/content/concept/StorageContainerManager.md b/hadoop-hdds/docs/content/concept/StorageContainerManager.md
index b434ae1..68953ce 100644
--- a/hadoop-hdds/docs/content/concept/StorageContainerManager.md
+++ b/hadoop-hdds/docs/content/concept/StorageContainerManager.md
@@ -87,8 +87,6 @@
* Block data is deleted in the background. Need a list to follow the progress.
* Valid cert, Revoked certs
* Used by the internal Certificate Authority to authorize other Ozone services
- * List of nodes
- * It's reported by the Datanodes via HB. *Not persisted*
## Notable configuration
diff --git a/hadoop-hdds/docs/content/design/ec.md b/hadoop-hdds/docs/content/design/ec.md
index 88d2c76..468e7ac 100644
--- a/hadoop-hdds/docs/content/design/ec.md
+++ b/hadoop-hdds/docs/content/design/ec.md
@@ -1,6 +1,6 @@
---
title: Erasure Coding in Ozone
-summary: Crypto key management to handle GDPR "right to be forgotten" feature
+summary: Use Erasure Coding algorithm for efficient storage
date: 2020-06-30
jira: HDDS-3816
status: draft
diff --git a/hadoop-hdds/docs/content/feature/HA.md b/hadoop-hdds/docs/content/feature/HA.md
index 456571b..116cbb7 100644
--- a/hadoop-hdds/docs/content/feature/HA.md
+++ b/hadoop-hdds/docs/content/feature/HA.md
@@ -28,7 +28,7 @@
To avoid any single point of failure the leader nodes also should have a HA setup.
1. HA of Ozone Manager is implemented with the help of RAFT (Apache Ratis)
- 2. HA of Storage Container Manager is [under implementation]({{< ref "omha.md">}})
+ 2. HA of Storage Container Manager is [under implementation]({{< ref "scmha.md">}})
## Ozone Manager HA
