@@ -199,16 +199,17 @@ asserts
199199.. serverstatus:: asserts
200200
201201 A document that reports on the number of assertions raised since the
202- MongoDB process started. While assert errors are typically uncommon,
203- if there are non-zero values for the :serverstatus:`asserts`, you
204- should examine the log file for more information. In many cases,
205- these errors are trivial, but are worth investigating.
202+ MongoDB process started. Assertions are internal checks for errors that
203+ occur while the database is operating and can help diagnose issues with the
204+ MongoDB server. Non-zero asserts values indicate assertion errors, which are
205+ uncommon and not an immediate cause for concern. Errors that generate asserts
206+ can be recorded in the log file or returned directly to a client application
207+ for more information.
206208
207209.. serverstatus:: asserts.regular
208210
209211 The number of regular assertions raised since the MongoDB process
210- started. Examine the log file for more information about these
211- messages.
212+ started. Examine the MongoDB log for more information.
212213
213214.. serverstatus:: asserts.warning
214215
@@ -226,7 +227,8 @@ asserts
226227 the MongoDB process started. These are errors that user may
227228 generate, such as out of disk space or duplicate key. You can
228229 prevent these assertions by fixing a problem with your application
229- or deployment. Examine the MongoDB log for more information.
230+ or deployment. Examine the log file for more information about these
231+ messages.
230232
231233.. serverstatus:: asserts.rollovers
232234
0 commit comments