addressed reviewers feedback

Author: lilyjma

articles/azure-functions/create-first-function-cli-typescript.md

@@ -194,7 +194,7 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
 
     Toward the end of the output, the following should appear:
 
-    ![Terminal window output when running function locally](./media/functions-create-first-azure-function-azure-cli/functions-test-local-terminal.png)
+    ![Screenshot of terminal window output when running function locally.](./media/functions-create-first-azure-function-azure-cli/functions-test-local-terminal.png)
 
     >[!NOTE]
     > If HttpExample doesn't appear as shown below, you likely started the host from outside the root folder of the project. In that case, use **Ctrl**+**C** to stop the host, navigate to the project's root folder, and run the previous command again.
@@ -226,6 +226,7 @@ Each binding requires a direction, a type, and a unique name. The HTTP trigger h
     ```
 
     The [New-AzFunctionApp](/powershell/module/az.functions/new-azfunctionapp) cmdlet creates the function app in Azure. It's recommended that you use the latest version of Node.js, which is currently 18. You can specify the version by setting `--runtime-version` to `18`.
+    
     ---
 
     In the previous example, replace `<STORAGE_NAME>` with the name of the account you used in the previous step, and replace `<APP_NAME>` with a globally unique name appropriate to you. The `<APP_NAME>` is also the default DNS domain for the function app.

articles/azure-functions/create-first-function-vs-code-node.md

@@ -174,7 +174,7 @@ Use the table below to resolve the most common issues encountered when using thi
 |Problem|Solution|
 |--|--|
 |Can't create a local function project?|Make sure you have the [Azure Functions extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions) installed.|
-|Can't run the function locally?|Make sure you have the lastest version of [Azure Functions Core Tools installed](functions-run-local.md?tabs=node) installed. <br/>When running on Windows, make sure that the default terminal shell for Visual Studio Code isn't set to WSL Bash.|
+|Can't run the function locally?|Make sure you have the latest version of [Azure Functions Core Tools installed](functions-run-local.md?tabs=node) installed. <br/>When running on Windows, make sure that the default terminal shell for Visual Studio Code isn't set to WSL Bash.|
 |Can't deploy function to Azure?|Review the Output for error information. The bell icon in the lower right corner is another way to view the output. Did you publish to an existing function app? That action overwrites the content of that app in Azure.|
 |Couldn't run the cloud-based Function app?|Remember to use the query string to send in parameters.|
 

includes/functions-run-function-test-local-cli.md

@@ -17,7 +17,7 @@ ms.custom: devdivchpfy22
 
     Toward the end of the output, the following lines must appear:
 
-    ![Terminal window output when running function locally](../articles/azure-functions/media/functions-create-first-azure-function-azure-cli/functions-test-local-terminal.png)
+    ![Screenshot of terminal window output when running function locally.](../articles/azure-functions/media/functions-create-first-azure-function-azure-cli/functions-test-local-terminal.png)
     
     >[!NOTE]  
     > If HttpExample doesn't appear as shown above, you likely started the host from outside the root folder of the project. In that case, use **Ctrl**+**C** to stop the host, go to the project's root folder, and run the previous command again.