diff --git a/content/operate/rc/api/examples/audit-system-logs.md b/content/operate/rc/api/examples/audit-system-logs.md
index 6e8f25daa9..a83e9a800a 100644
--- a/content/operate/rc/api/examples/audit-system-logs.md
+++ b/content/operate/rc/api/examples/audit-system-logs.md
@@ -1,14 +1,14 @@
 ---
-Title: Audit using Service Log
+Title: Audit using System Log
 alwaysopen: false
 categories:
 - docs
 - operate
 - rc
-description: Use the service log to track and audit actions performed in the account
+description: Use the system log to track and audit actions performed in the account.
 weight: 60
 ---
-Service logs collect and report actions performed on various entities in your Redis Cloud subscription.  These entities include the account itself, users, API Keys, subscriptions, databases, accounts, payment methods, and more. For each entity, various lifecycle events are logged in the system log.
+System logs collect and report actions performed on various entities in your Redis Cloud subscription.  These entities include the account itself, users, API Keys, subscriptions, databases, accounts, payment methods, and more. For each entity, various lifecycle events are logged in the system log.
 
 To view the log, sign in to the [Redis Cloud console](https://cloud.redis.io/) and then select **Logs** from the main menu.
 
@@ -18,7 +18,7 @@ To learn more, see [System logs]({{< relref "/operate/rc/logs-reports/system-log
 
 ## Get system logs via REST API
 
-The REST API operation for querying the system service log is [`GET /logs`]({{< relref "/operate/rc/api/api-reference#tag/Account/operation/getAccountSystemLogs" >}}).
+The REST API operation for querying the system log is [`GET /logs`]({{< relref "/operate/rc/api/api-reference#tag/Account/operation/getAccountSystemLogs" >}}).
 
 The `/logs` API operation accepts the following parameters:
 
diff --git a/content/operate/rc/api/get-started/process-lifecycle.md b/content/operate/rc/api/get-started/process-lifecycle.md
index 543a232eae..b302102bc8 100644
--- a/content/operate/rc/api/get-started/process-lifecycle.md
+++ b/content/operate/rc/api/get-started/process-lifecycle.md
@@ -10,7 +10,7 @@ description: API requests follow specific lifecycle phases and states, based on
 linkTitle: API request lifecycle
 weight: 60
 ---
-Redis Cloud owners and viewers can leverage a RESTful API that permits operations against a variety of resources, including subscriptions, databases, and related infrastructure.
+Redis Cloud owners and viewers can leverage a REST API that permits operations against a variety of resources, including subscriptions, databases, and related infrastructure.
 
 [Once it's enabled]({{< relref "/operate/rc/api/get-started/enable-the-api.md" >}}), you can use the REST API to create, update, and delete subscriptions, databases, and other entities.
 
@@ -28,11 +28,11 @@ During this phase, the request is received, evaluated, planned, and executed.
 
 ### Use tasks to track requests
 
-Many operations are asychronous, including CREATE, UPDATE, and DELETE operations.  The response objects for such operations provide a `taskId` identifier that lets you track the progress of the underlying operation.
+The response objects for all asynchronous operations provide a `taskId` identifier that lets you track the progress of the underlying operation.
 
 You can query the `taskId` to track the state of a specific task using [`GET /v1/tasks/{taskId}`]({{< relref "/operate/rc/api/api-reference#tag/Tasks/operation/getTaskById" >}}).
 
-You can also query the state of all active tasks or recently completed tasks in your account using [`GET /tasks`]({{< relref "/operate/rc/api/api-reference#tag/Tasks/operation/getAllTasks" >}})
+You can also query the state of all active tasks or recently completed tasks in your account using [`GET /tasks`]({{< relref "/operate/rc/api/api-reference#tag/Tasks/operation/getAllTasks" >}}).
 
 ### Task process states