(DOCSP-45941) Revises per explicit edits from v1 review. (#56)

Author: erabil-mdb

source/auditing-logging.txt

@@ -25,7 +25,8 @@ Features
 Auditing
 ````````
 
-Database auditing lets you track system activity for deployments with
+Available on ``M10+`` {+clusters+}, database auditing lets you track system 
+activity for deployments with
 multiple users. As a |service| administrator, you can:
 
 - Rely on default auditing settings in |service|. By default, |service|
@@ -60,9 +61,8 @@ Accessing Audit Logs
 
 .. include:: /includes/cloud-docs/logs.rst
 
-To retrieve the audit logs using the {+atlas-admin-api+}, see
-:oas-atlas-op:`Logs </downloadLogsForOneClusterHostInOneProject>`. You
-can use these API commands:
+To return and update your audit configuration per project, use the following 
+`Atlas Administration API <https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/>`__ commands:
 
 - :ref:`atlas-auditing-describe <atlas-auditing-describe>` returns the
   auditing configuration for the specified project.
@@ -83,8 +83,11 @@ the ``mongodb.log``, and :ref:`the project activity feed <view-activity-feed>`.
 Recommendations for Auditing
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-For development and testing environments, do not enable auditing. This
-saves costs in your non-production environments.
+We recommend that you enable auditing when you provision your {+clusters+}. 
+However, auditing puts additional load on your {+clusters+} and increases costs. 
+To optimize costs, you can disable auditing in lower environments for development. 
+Certain industries, like healthcare and financial services, may opt to keep 
+auditing enabled in development for compliance reasons.
 
 For staging and production environments, enable auditing for
 additional security. We recommend that you audit the following events at a minimum:
@@ -126,15 +129,15 @@ Recommendations for Audit Logs
 To integrate with tools beyond the built-in integrations, we recommend
 that you retrieve logs with the following tools and feed the JSON-formatted output to your external tools:
 
+- If you use |aws|, you can continually push logs to an |aws| S3
+  bucket. To learn more, see the
+  :oas-atlas-tag:`Push-Based Log Export <Push-Based-Log-Export>` {+atlas-admin-api+} endpoints.
+- Use the {+atlas-admin-api+} endpoints for :oas-atlas-tag:`Logs <MongoDB-Cloud-Users>` and :oas-atlas-tag:`Project Events <Events>` to
+  retrieve deployment logs and lists of project events.
 - Use the ``atlas deployments logs`` command in the {+atlas-cli+}
   to retrieve deployment logs. To learn more,
   see :atlas:`Atlas Deployment Logs 
   </cli/current/command/atlas-deployments-logs/>`.
-- Use the {+atlas-admin-api+} endpoints for :oas-atlas-tag:`Logs <MongoDB-Cloud-Users>` and :oas-atlas-tag:`Project Events <Events>` to
-  retrieve deployment logs and lists of project events.
-- If you use |aws|, you can continually push logs to an |aws| S3
-  bucket. To learn more, see the
-  :oas-atlas-tag:`Push-Based Log Export <Push-Based-Log-Export>` {+atlas-admin-api+} endpoints.
 
 Examples
 --------

source/includes/cloud-docs/logs.rst

@@ -1,6 +1,7 @@
+|service| retains the last 30 days of log messages and
+system event audit messages.
 You can download |service| logs at any point until the end of their
 retention periods by using the {+atlas-ui+}, {+atlas-admin-api+}, and
-{+atlas-cli+}. |service| retains the last 30 days of log messages and
-system event audit messages.
+{+atlas-cli+}.
 
 To learn more, see :ref:`mongodb-logs`.