Update functions-event-grid-blob-trigger.md

Starting only the blob service will lead to exception "Azure.Core: No connection could be made because the target machine actively refused it. (127.0.0.1:10001)" because a blob trigger also needs a queue service to handle poison blobs. Best to use the general Azurite: Start command to run all services

Author: mickey-stringer

articles/azure-functions/functions-event-grid-blob-trigger.md

@@ -273,7 +273,7 @@ Visual Studio Code uses Azurite to emulate Azure Storage services when running l
 
 1. Verify that the *local.settings.json* file has `"UseDevelopmentStorage=true"` set for `AzureWebJobsStorage`, which tells Core Tools to use Azurite instead of a real storage account connection when running locally. 
 
-1. Press F1 to open the command palette, type `Azurite: Start Blob Service`, and press enter, which starts the Azurite Blob Storage service emulator.
+1. Press F1 to open the command palette, type `Azurite: Start`, and press enter, which starts the Azurite Storage services emulator.
 
 1. Select the Azure icon in the Activity bar, expand **Workspace** > **Attached Storage Accounts** > **Local Emulator**, right-click **Blob Containers**, select **Create Blob Container...**, enter the name `samples-workitems`, and press Enter.