Merge pull request #2322 from redis/DOC-5874

RC: Modify process lifecycle to make clearer that some GET requests require extra processing

Author: cmilesb

content/operate/rc/api/get-started/process-lifecycle.md

@@ -14,9 +14,9 @@ Redis Cloud owners and viewers can leverage a REST API that permits operations a
 
 [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.
 
-All create, update, and delete API operations (`POST`, `PUT`, and `DELETE`) and some query operations (`GET`) run asynchronously, which means that provisioning occurs in the background.  When you submit a request, a background process, known as a **Task**, starts working on it.  The response object includes an ID that lets you determine the status of the background process as it performs its work.
+All create, update, and delete API operations (`POST`, `PUT`, and `DELETE`) and some query operations (`GET`) run asynchronously, which means that provisioning or processing occurs in the background.  When you submit a request, a background process, known as a **Task**, starts working on it.  The response object includes an ID that lets you determine the status of the background process as it works.
 
-For operations that do not create or modify resources (such as most GET operations), the API is synchronous; that is, the response object reports the results of the request.
+For operations that do not create or modify resources or do not require additional processing (such as most GET operations), the API is synchronous; that is, the response object reports the results of the request.
 
 Asynchronous operations have two main phases: processing and provisioning.  A resource is not available until both phases are complete.