Edit typos

Author: ggailey777

articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0011.md

@@ -20,15 +20,15 @@ This event occurs when a function app doesn't have the `FUNCTIONS_WORKER_RUNTIME
 
 The `FUNCTIONS_WORKER_RUNTIME` application setting indicates the language or language stack on which the function app runs, such as `python`. For more information on valid values, see the [`FUNCTIONS_WORKER_RUNTIME`](../../functions-app-settings.md#functions_worker_runtime) reference.
 
-While note currently required, you should always specify `FUNCTIONS_WORKER_RUNTIME` for your function apps. If you don't use setting and the Functions host can't determine the correct language or language stack, you might see exceptions or unexpected behaviors. 
+While not currently required, you should always specify `FUNCTIONS_WORKER_RUNTIME` for your function apps. When you don't have this setting and the Functions host can't determine the correct language or language stack, you might see exceptions or unexpected behaviors. 
 
-Because `FUNCTIONS_WORKER_RUNTIME` is likely to become a required setting, you should explicitly set it in all of your existing function apps and deployment scripts to prevent any future downtime.
+Because `FUNCTIONS_WORKER_RUNTIME` is likely to become a required setting, you should explicitly set it in all of your existing function apps and deployment scripts to prevent any downtime in the future.
 
 ## How to resolve the event
 
 In a production application, add `FUNCTIONS_WORKER_RUNTIME` to the [application settings](../../functions-how-to-use-azure-function-app-settings.md#settings).
 
-When running locally in Azure Functions Core Tools, add `FUNCTIONS_WORKER_RUNTIME` to the [local.settings.json file](../../functions-develop-local.md#local-settings-file).
+When running locally in Azure Functions Core Tools, also add `FUNCTIONS_WORKER_RUNTIME` to the [local.settings.json file](../../functions-develop-local.md#local-settings-file).
 
 ## When to suppress the event