More minor updates

Author: codingbandit

09_Vector_Search_Cosmos_DB/README.md

@@ -120,7 +120,7 @@ The following is an example of a vector indexing policy.
 
 ## Lab - Use vector search on embeddings in Azure Cosmos DB for NoSQL
 
-In this lab, a notebook demonstrates how to add an embedding field to a document, create a vector search index, and perform a vector search query. The notebook ends with a demonstration of utilizing vector search with an LLM in a RAG scenario using Azure OpenAI.
+In this lab, a notebook demonstrates how to add an embedding field to a document, create a container capable of vector search, and perform a vector search query. The notebook ends with a demonstration of utilizing vector search with an LLM in a RAG scenario using Azure OpenAI.
 
 This lab requires the Azure OpenAI endpoint and access key to be added to the settings (`.env`) file. Access this information by opening [Azure OpenAI Studio](https://oai.azure.com/portal) and selecting the **Gear**/Settings icon located to the right in the top toolbar.
 

11_Backend_API/README.md

@@ -8,4 +8,4 @@ This lab also requires the data provided in the previous lab titled [Load data i
 
 >**Note**: It is highly recommended to use a [virtual environment](https://python.land/virtual-environments/virtualenv) for all labs.
 
-Please visit the lab repository to complete [this lab](../Labs/lab_4_langchain.ipynb).
+Please visit the lab repository to complete [this lab](../Labs/lab_5_backend_api.md).

Labs/lab_5_backend_api.md

@@ -200,8 +200,6 @@ The last step is to deploy the backend api container image to Azure Container Ap
     az containerapp up --name <container app name> --image <login server>/devguidebackendapi:v1 --resource-group <resource group name> --environment <container app environment name> --ingress external
     ```
 
-    ![The console output of the container app up command displays with the endpoint highlighted.](media/container_deploy.png)
-
 9. In the Azure Portal, locate and open the **Container App** resource ending in `-api`.
 
 10. From the left menu, expand the **Application** section and select **Revisions and replicas**. Notice screen, there is a failed container revision (may need to select **Refresh** from the top toolbar menu). This is because the `hello-world` container is running at the same binding address as the backend api container.