Misc docs improvements (#2163)

Author: deliahu

docs/clusters/management/create.md

@@ -50,7 +50,7 @@ node_groups:
     spot: false
   # ...
 
-# subnet visibility [public (instances will have public IPs) | private (instances will not have public IPs)]
+# subnet visibility for instances [public (instances will have public IPs) | private (instances will not have public IPs)]
 subnet_visibility: public
 
 # NAT gateway (required when using private subnets) [none | single | highly_available (a NAT gateway per availability zone)]

docs/workloads/async/example.md

@@ -145,7 +145,7 @@ curl http://<load_balancer_url>/iris-classifier/<id>  # <id> is the request id t
 
 Depending on the status of your workload, you will get different responses back. The possible workload status
 are `in_queue | in_progress | failed | completed`. The `result` and `timestamp` keys are returned if the status
-is `completed`.
+is `completed`. The result will remain queryable for 7 days after the request was completed.
 
 It is also possible to setup a webhook in your handler to get the response sent to a pre-defined web server once the
 workload completes or fails. You can read more about it in the [webhook documentation](./webhooks.md).

docs/workloads/async/handler.md

@@ -73,7 +73,7 @@ class Handler:
             request_id (optional): The request id string that identifies a workload
 
         Returns:
-            Workload result or batch of results.
+            JSON-serializeable result.
         """
         pass
 ```
@@ -192,7 +192,8 @@ class Handle:
 
 ## API responses
 
-Currently, AsyncAPI responses of your `handle_async()` method have to be a JSON-serializable dictionary.
+The return value of your `handle_async()` method must be a JSON-serializable dictionary. The result for
+each request will remain queryable for 7 days after the request was completed.
 
 ## Chaining APIs