upload changes

Author: spelluru

articles/event-grid/handler-event-hubs.md

@@ -15,7 +15,7 @@ An event handler is the place where the event is sent. The handler takes an acti
 
 Use **Event Hubs** when your solution gets events from Event Grid faster than it can process the events. Once the events are in an event hub, your application can process events from the event hub at its own schedule. You can scale your event processing to handle the incoming events.
 
-## Examples
+## Tutorials
 See the following examples: 
 
 |Title  |Description  |

articles/event-grid/handler-functions.md

@@ -18,7 +18,7 @@ Use **Azure Functions** in a serverless architecture to respond to events from E
 
 For more information, see [Event Grid trigger for Azure Functions](../azure-functions/functions-bindings-event-grid.md) for an overview of using the Event Grid trigger in functions.
 
-## Examples
+## Tutorials
 
 |Title  |Description  |
 |---------|---------|

articles/event-grid/handler-storage-queues.md

@@ -15,7 +15,7 @@ An event handler is the place where the event is sent. The handler takes some fu
 
 Use **Queue Storage** to receive events that need to be pulled. You might use Queue storage when you have a long running process that takes too long to respond. By sending events to Queue storage, the app can pull and process events on its own schedule.
 
-## Examples
+## Tutorials
 See the following tutorial for an example of using Queue storage as an event handler. 
 
 |Title  |Description  |