reviews

Author: jgao54

docs/integrations/data-ingestion/clickpipes/mongodb/add_table.md

@@ -1,6 +1,6 @@
 ---
 title: 'Adding specific tables to a ClickPipe'
-description: 'Describes the steps need to add specific tables to a ClickPipe.'
+description: 'Describes the steps needed to add specific tables to a ClickPipe.'
 sidebar_label: 'Add Table'
 slug: /integrations/clickpipes/mongodb/add_table
 show_title: false

docs/integrations/data-ingestion/clickpipes/mongodb/index.md

@@ -23,13 +23,17 @@ import Image from '@theme/IdealImage';
 Currently, ingesting data from MongoDB to ClickHouse Cloud via ClickPipes is in Private Preview.
 :::
 
-You can use ClickPipes to ingest data from your MongoDB database into ClickHouse Cloud. The source MongoDB database can be hosted on-premises or in the cloud using services like Mongo Atlas.
+:::note
+In the ClickHouse Cloud console and documentation, "table" and "collection" are used interchangeably for MongoDB.
+:::
+
+You can use ClickPipes to ingest data from your MongoDB database into ClickHouse Cloud. The source MongoDB database can be hosted on-premises or in the cloud using services like MongoDB Atlas.
 
 ## Prerequisites {#prerequisites}
 
 To get started, you first need to ensure that your MongoDB database is correctly configured for replication. The configuration steps depend on how you're deploying MongoDB, so please follow the relevant guide below:
 
-1. [Mongo Atlas](./mongodb/source/atlas)
+1. [MongoDB Atlas](./mongodb/source/atlas)
 
 2. [Generic MongoDB](./mongodb/source/generic)
 
@@ -39,7 +43,6 @@ Once your source MongoDB database is set up, you can continue creating your Clic
 
 Make sure you are logged in to your ClickHouse Cloud account. If you don't have an account yet, you can sign up [here](https://cloud.clickhouse.com/).
 
-[//]: # (   TODO update image here)
 1. In the ClickHouse Cloud console, navigate to your ClickHouse Cloud Service.
 
 <Image img={cp_service} alt="ClickPipes service" size="lg" border/>

docs/integrations/data-ingestion/clickpipes/mongodb/pause_and_resume.md

@@ -27,7 +27,7 @@ There are scenarios where it would be useful to pause a MongoDB ClickPipe. For e
 <Image img={pause_dialog} border size="md"/>
 
 4. Head over to the **Metrics** tab.
-5. In around 5 seconds (and also on page refresh), the status of the pipe should be **Paused**.
+5. Wait for the status of the pipe to be **Paused**.
 
 <Image img={pause_status} border size="md"/>
 
@@ -43,4 +43,4 @@ There are scenarios where it would be useful to pause a MongoDB ClickPipe. For e
 <Image img={resume_dialog} border size="md"/>
 
 5. Head over to the **Metrics** tab.
-6. In around 5 seconds (and also on page refresh), the status of the pipe should be **Running**.
+6. Wait for the status of the pipe to be **Running**.

docs/integrations/data-ingestion/clickpipes/mongodb/resync.md

@@ -41,5 +41,5 @@ since initial load with parallel threads is involved each time.
 
 4. A dialog box should appear for confirmation. Click on Resync again.
 5. Head over to the **Metrics** tab.
-6. In around 5 seconds (and also on page refresh), the status of the pipe should be **Setup** or **Snapshot**.
+6. Wait for the status of the pipe to be **Setup** or **Snapshot**.
 7. The initial load of the resync can be monitored in the **Tables** tab - in the **Initial Load Stats** section.

docs/integrations/data-ingestion/clickpipes/mongodb/source/atlas.md

@@ -1,8 +1,8 @@
 ---
-sidebar_label: 'Mongo Atlas'
-description: 'Step-by-step guide on how to set up Mongo Atlas as a source for ClickPipes'
+sidebar_label: 'MongoDB Atlas'
+description: 'Step-by-step guide on how to set up MongoDB Atlas as a source for ClickPipes'
 slug: /integrations/clickpipes/mongodb/source/atlas
-title: 'Mongo Atlas source setup guide'
+title: 'MongoDB Atlas source setup guide'
 ---
 
 import mongo_atlas_configuration from '@site/static/images/integrations/data-ingestion/clickpipes/mongodb/mongo-atlas-cluster-overview-configuration.png'
@@ -13,13 +13,13 @@ import mongo_atlas_add_roles from '@site/static/images/integrations/data-ingesti
 import mongo_atlas_restrict_access from '@site/static/images/integrations/data-ingestion/clickpipes/mongodb/mongo-atlas-restrict-access.png'
 import Image from '@theme/IdealImage';
 
-# Mongo Atlas source setup guide
+# MongoDB Atlas source setup guide
 
 ## Configure oplog retention {#enable-oplog-retention}
 
 Minimum oplog retention of 24 hours is required for replication. We recommend setting the oplog retention to 72 hours or longer to ensure that the oplog is not truncated before the initial snapshot is completed. To set the oplog retention via UI:
 
-1. Navigate to your cluster's `Overview` tab in the Atlas console and click on the `Configuration` tab.
+1. Navigate to your cluster's `Overview` tab in the MongoDB Atlas console and click on the `Configuration` tab.
 <Image img={mongo_atlas_configuration} alt="Navigate to cluster configuration" size="lg" border/>
 
 2. Click `Additional Settings` and scroll down to `More Configuration Options`.
@@ -32,7 +32,7 @@ Minimum oplog retention of 24 hours is required for replication. We recommend se
 
 ## Configure a database user {#configure-database-user}
 
-Once you are logged in to your Atlas console, click `Database Access` under the Security tab in the left navigation bar. Click on "Add New Database User". 
+Once you are logged in to your MongoDB Atlas console, click `Database Access` under the Security tab in the left navigation bar. Click on "Add New Database User".
 
 ClickPipes requires password authentication:
 
@@ -43,7 +43,7 @@ ClickPipes requires a user with the following roles:
 - `readAnyDatabase`
 - `clusterMonitor`
 
-You can find them in the `Specific Priviledges` section:
+You can find them in the `Specific Privileges` section:
 
 <Image img={mongo_atlas_add_roles} alt="Configure user roles" size="lg" border/>
 

docs/integrations/data-ingestion/clickpipes/mongodb/source/generic.md

@@ -20,10 +20,10 @@ Minimum oplog retention of 24 hours is required for replication. We recommend se
 You can check your current oplog retention by running the following command in the MongoDB shell (you must have `clusterMonitor` role to run this command):
 
 ```javascript
-db.serverStatus().oplogTruncation.oplogMinRetentionHours
+db.getSiblingDB("admin").serverStatus().oplogTruncation.oplogMinRetentionHours
 ```
 
-To set the oplog retention to 72 hours, run the following command as an admin user:
+To set the oplog retention to 72 hours, run the following command on each node in the replica set as an admin user:
 
 ```javascript
 db.adminCommand({
@@ -32,13 +32,14 @@ db.adminCommand({
 })
 ```
 
+For more details on the `replSetResizeOplog` command and oplog retention, see [MongoDB documentation](https://www.mongodb.com/docs/manual/reference/command/replSetResizeOplog/).
+
 ## Configure a database user {#configure-database-user}
 
 Connect to your MongoDB instance as an admin user and execute the following command to create a user for MongoDB CDC ClickPipes:
 
 ```javascript
-use admin;
-db.createUser({
+db.getSiblingDB("admin").createUser({
     user: "clickpipes_user",
     pwd: "some_secure_password",
     roles: ["readAnyDatabase", "clusterMonitor"],