Skip to content

Commit 73b2030

Browse files
committed
updated as per your suggestion
1 parent a3e00f5 commit 73b2030

File tree

3 files changed

+15
-15
lines changed

3 files changed

+15
-15
lines changed

docs/MongoDB/mongodb-create-backup.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -80,9 +80,9 @@ graph TD;
8080
F --> B
8181
```
8282

83-
### Notes
84-
> - Ensure the `mongod` server is running before executing the `mongodump` or `mongorestore` commands.
85-
> - Use appropriate options with `mongodump` to back up specific databases or collections.
86-
> - The backup directory should be accessible and writable by the MongoDB instance.
87-
83+
:::note
84+
- Ensure the `mongod` server is running before executing the `mongodump` or `mongorestore` commands.
85+
- Use appropriate options with `mongodump` to back up specific databases or collections.
86+
- The backup directory should be accessible and writable by the MongoDB instance.
87+
:::
8888
Creating backups regularly ensures that you have a recovery option in case of data loss or corruption.

docs/MongoDB/mongodb-deployment.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -79,11 +79,11 @@ graph TD;
7979
H --> K[MMS]
8080
```
8181

82-
### Notes
83-
84-
> - Regularly prototype, test, and monitor your deployment environment.
85-
> - Use `mongostat` to check the status of your `mongod` instances and monitor database operations.
86-
> - Use `mongotop` to track and report read/write activity on a collection basis.
87-
> - Utilize MongoDB Management Service (MMS) for comprehensive monitoring and a visual dashboard.
82+
:::note
8883

84+
- Regularly prototype, test, and monitor your deployment environment.
85+
- Use `mongostat` to check the status of your `mongod` instances and monitor database operations.
86+
- Use `mongotop` to track and report read/write activity on a collection basis.
87+
- Utilize MongoDB Management Service (MMS) for comprehensive monitoring and a visual dashboard.
88+
:::
8989
Having a well-planned and monitored deployment strategy ensures the stability and performance of your MongoDB in a production environment.

docs/MongoDB/mongodb-java-operations.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,10 +19,9 @@ Before you start using MongoDB in your Java programs, ensure that you have Mongo
1919
Make sure to download the latest release of these JAR files.
2020

2121
2. **Include the JAR files in your classpath**.
22-
23-
### Note:
22+
:::note
2423
You can download the JAR files from the [MongoDB Java Driver](https://mongodb.github.io/mongo-java-driver/) website.
25-
24+
:::
2625
## Connect to Database
2726

2827
To connect to a database, specify the database name. If the database doesn't exist, MongoDB creates it automatically.
@@ -439,11 +438,12 @@ graph TD;
439438
G --> H[Close MongoDB Client]
440439
```
441440

442-
## Notes
441+
:::note
443442

444443
- Ensure MongoDB is running before executing the Java programs.
445444
- Use appropriate exception handling in real-world applications to handle any database connection issues.
446445
- For more advanced usage and configurations, refer to the [MongoDB Java Driver Documentation](https://mongodb.github.io/mongo-java-driver/).
446+
:::
447447

448448
## Table of Methods
449449

0 commit comments

Comments
 (0)