diff --git a/content/operate/rc/api/get-started/process-lifecycle.md b/content/operate/rc/api/get-started/process-lifecycle.md
index b302102bc8..31b3a237d2 100644
--- a/content/operate/rc/api/get-started/process-lifecycle.md
+++ b/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.
 
diff --git a/content/operate/rc/api/how-to/manage-api-keys.md b/content/operate/rc/api/how-to/manage-api-keys.md
deleted file mode 100644
index a618e7f980..0000000000
--- a/content/operate/rc/api/how-to/manage-api-keys.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-Title: Manage API Keys
-alwaysopen: false
-categories:
-- docs
-- operate
-- rc
-description: Managing API Keys using the Redis Cloud admin console
-draft: true
-hidden: true
-weight: 30
----
-After you create a Redis Cloud API access key, you can manage your API access key in the following ways:
-
-- Deleting the access key
-- Limiting usage of the access key by network subnets
-<!-->
-## Delete an access key
-
-To delete an access key:
-
-1. [Log in to admin console](https://app.redislabs.com) as an account owner.
-1. Go to: **Settings** > **Cloud API Keys**
-
-    If **Cloud API Keys** is not shown, make sure you have [enabled the API for your account]({{< relref "/operate/rc/api/how-to/enable-your-account-to-use-api.md" >}})).
-1. Click **Delete**.
-1. Confirm that you want to delete the access key.
-
-## Limit access by subnet
-
-By default, API access is allowed from all IP addresses.
-
-To limit API access to a specified range of source IP addresses:
-
-1. [Log in to admin console](https://app.redislabs.com) as an account owner.
-1. Go to: **Settings** > **Cloud API Keys**
-1. Click **Manage IPs** for the access key that you want to limit.
-1. Click {{< image filename="/images/rs/icon_add.png#no-click" alt="Add" >}} to add a new whitelist subnet.
-1. Enter the subnet in [CIDR format](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation), for example: `10.2.5.0/24`
-1. Save the subnet.
-
-After you add the subnet, you can add more subnets or click **OK**.
-
-## Delete an allowed subnet
-
-1. [Log in to admin console](https://app.redislabs.com) as an account owner.
-1. Go to: **Settings** > **Cloud API Keys**
-1. Click **Manage IPs** for the access key that you want to change.
-1. Delete the subnet that you want to disallow.
-
-After you delete the subnet, you can delete more subnets or click **OK**.
--->
\ No newline at end of file
diff --git a/content/operate/rc/api/how-to/metrics-and-performance-data.md b/content/operate/rc/api/how-to/metrics-and-performance-data.md
deleted file mode 100644
index 102be8382a..0000000000
--- a/content/operate/rc/api/how-to/metrics-and-performance-data.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-Title: Metrics and Usage Statistics
-alwaysopen: false
-categories:
-- docs
-- operate
-- rc
-description: Using the metrics API operation to query database usage and statistics
-  information
-draft: true
-weight: 80
----
-You can get metrics and usage statistics for a database from the API operation:
-
-`GET /subscriptions/{subscription-id}/databases/{database-id}/metrics?metricSpan={metric-span}`.
-
-The metrics API is supported for Redis Cloud Pro subscriptions.
-
-The query accepts 3 parameters:
-
-- `subscription-id` (Required) - The relevant subscription ID for the database
-- `database-id` (Required) - The ID of the database
-- `metric-span` (Optional) - The [time span]({{< relref "/operate/rc/api/concepts/metrics#metric-spans-and-intervals" >}}) for the query. The default time span is `1hour`.
-
-## Metrics query example
-
-```shell
-{{% embed-code "rv/api/70-query-metrics.sh" %}}
-```