Add some extra ideas cribbed from Matt's demo

Author: babbageclunk

cosmos-todo-list/README.md

@@ -52,9 +52,13 @@ You can monitor their progress with:
 ```sh
 watch kubectl get -n cosmosdb resourcegroup,databaseaccount,sqldatabase,sqldatabasecontainer
 ```
-
 You can also find the resource group in the [Azure portal](https://portal.azure.com) and watch the Cosmos DB resources being created there.
 
+It could take a few minutes for the Cosmos DB resources to be provisioned.
+In that time you might see some `ResourceNotFound` errors, or messages indicating that the database account isn't ready, on the SQL database or container.
+This is OK!
+The operator will keep creating them once the account is available and the errors should eventually resolve themselves.
+
 ## Create the `cosmos-settings` secret
 
 We need to provide the web application with access to the database.
@@ -64,6 +68,9 @@ COSMOS_DB_ACCOUNT="$(az cosmosdb show --resource-group aso-cosmos-demo --name sa
 COSMOS_DB_KEY="$(az cosmosdb keys list --resource-group aso-cosmos-demo --name sampledbaccount -otsv --query 'primaryMasterKey')"
 ```
 
+Another option is to get the account URI and key from the [portal](https://portal.azure.com).
+You can find them on the Keys page of the Cosmos DB account.
+
 Then create the secret the pod will use with:
 ```sh
 kubectl --namespace cosmosdb create secret generic cosmos-settings \
@@ -73,7 +80,7 @@ kubectl --namespace cosmosdb create secret generic cosmos-settings \
         --from-literal=ContainerName="sample-sql-container"
 ```
 
-(Secret handling is an area we're still working on in ASO - in the future the operator should automatically get these details from Azure and create the secret itself once the database account is ready.)
+(Secret handling is an area we're still working on in ASO - in the future the operator should automatically get these details from Azure and create the secret itself once the database account is ready. See [#1471](https://github.com/Azure/azure-service-operator/issues/1471) for more details.)
 
 ## Deploy the web application
 
@@ -95,5 +102,18 @@ kubectl port-forward -n cosmosdb service/cosmos-todo-service 8080:80
 ```
 
 Now visiting [http://localhost:8080](http://localhost:8080) in your browser will hit the Cosmos DB application.
+You can create todo items and mark them as complete!
+
+Use the Cosmos DB account Data Explorer on the portal to expand the database and container, and you can see the todo-list items stored by the web app.
 
 If you're interested in how the todo application uses the Cosmos DB API, the code is available [here](https://github.com/Azure-Samples/cosmos-dotnet-core-todo-app/tree/main/src).
+
+## Clean up
+
+When you're finished with the sample application you can clean all of the Kubernetes and Azure resources up by deleting the `cosmosdb` namespace in your cluster.
+```sh
+kubectl delete namespace cosmosdb
+```
+
+Kubernetes will delete the web application pod and the operator will delete the Azure resource group and all the Cosmos DB resources.
+(Deleting a Cosmos DB account can take several minutes.)