fix(RUNNER-7473): Archive remaining unused Custom API configs (#143)

- Added a note regarding clean up for unused custom APIs

Author: YevSent

src/pages/guides/using/creating_rest_apis.md

@@ -1,5 +1,7 @@
 # Creating REST APIs
 
+> Note: IO Runtime cleans up custom APIs that have not been accessed for 90 days.
+
 You can create REST APIs from web actions you’ve deployed to Adobe I/O Runtime. Let’s assume that you’ve created four actions to manage CRUD operations for the `pet` entity:
 
 
@@ -26,7 +28,7 @@ Let’s see how you can create this API, assuming you have the web actions a
 
 When creating or updating a REST API, it can take up to 5 minutes to see the changes. 
 
-## Using wsk CLI
+## Using AIO CLI
 
 Using the `aio rt:api:create` command, you create each API endpoint one-by-one. This command allows you to set a base path, path, method, and response type. We will set:
 
@@ -298,4 +300,4 @@ Requests that have the requests originating from the IP addresses in the disallo
   "message":"Access from your IP address is not authorized"
 }
 ```
-> Make sure that the `my-require-gw-validation-web-action` is configured to be a web action with `-a require-gw-validation true`, otherwise the action can be accessed publicly without any restrictions on the non api url. 
+> Make sure that the `my-require-gw-validation-web-action` is configured to be a web action with `-a require-gw-validation true`, otherwise the action can be accessed publicly without any restrictions on the non api url.