Skip to content

Commit d0e4731

Browse files
committed
Acrolynx
1 parent 4ddcde2 commit d0e4731

File tree

1 file changed

+6
-8
lines changed

1 file changed

+6
-8
lines changed

articles/event-hubs/event-hubs-node-get-started-send.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ If you're new to Azure Event Hubs, see [Event Hubs overview](event-hubs-about.md
1717

1818
To complete this quickstart, you need the following prerequisites:
1919

20-
- **Microsoft Azure subscription**. To use Azure services, including Azure Event Hubs, you need a subscription. If you don't have an existing Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/) or use your MSDN subscriber benefits when you [create an account](https://azure.microsoft.com).
20+
- **Microsoft Azure subscription**. To use Azure services, including Azure Event Hubs, you need a subscription. If you don't have an existing Azure account, you can sign up for a [free trial](https://azure.microsoft.com/free/).
2121
- Node.js LTS. Download the latest [long-term support (LTS) version](https://nodejs.org).
2222
- Visual Studio Code (recommended) or any other integrated development environment (IDE).
2323
- **Create an Event Hubs namespace and an event hub**. The first step is to use the [Azure portal](https://portal.azure.com) to create a namespace of type Event Hubs, and obtain the management credentials your application needs to communicate with the event hub. To create a namespace and an event hub, follow the procedure in [this article](event-hubs-create.md).
@@ -139,16 +139,14 @@ In this section, you create a JavaScript application that sends events to an eve
139139
---
140140

141141
1. Run `node send.js` to execute this file. This command sends a batch of three events to your event hub. If you're using the Passwordless (Azure Active Directory's Role-based Access Control) authentication, you might want to run `az login` and sign into Azure using the account that was added to the Azure Event Hubs Data Owner role.
142-
1. In the Azure portal, verify that the event hub has received the messages. Refresh the page to update the chart. It might take a few seconds for it to show that the messages have been received.
142+
1. In the Azure portal, verify that the event hub received the messages. Refresh the page to update the chart. It might take a few seconds for it to show that the messages are received.
143143

144144
[![Verify that the event hub received the messages](./media/node-get-started-send/verify-messages-portal.png)](./media/node-get-started-send/verify-messages-portal.png#lightbox)
145145

146146
> [!NOTE]
147147
> For the complete source code, including additional informational comments, go to the [GitHub sendEvents.js page](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/eventhub/event-hubs/samples/v5/javascript/sendEvents.js).
148148

149-
You have now sent events to an event hub.
150-
151-
149+
152150
## Receive events
153151
In this section, you receive events from an event hub by using an Azure Blob storage checkpoint store in a JavaScript application. It performs metadata checkpoints on received messages at regular intervals in an Azure Storage blob. This approach makes it easy to continue receiving messages later from where you left off.
154152

@@ -170,13 +168,13 @@ To create an Azure storage account and a blob container in it, do the following
170168

171169
[Get the connection string to the storage account](../storage/common/storage-configure-connection-string.md).
172170

173-
Note the connection string and the container name. You use them in the receive code.
171+
Note the connection string and the container name. You use them in the code to receive events.
174172

175173
---
176174

177175
### Install the npm packages to receive events
178176

179-
For the receiving side, you need to install two more packages. In this quickstart, you use Azure Blob storage to persist checkpoints so that the program doesn't read the events that it has already read. It performs metadata checkpoints on received messages at regular intervals in a blob. This approach makes it easy to continue receiving messages later from where you left off.
177+
For the receiving side, you need to install two more packages. In this quickstart, you use Azure Blob storage to persist checkpoints so that the program doesn't read the events that it already read. It performs metadata checkpoints on received messages at regular intervals in a blob. This approach makes it easy to continue receiving messages later from where you left off.
180178
181179
### [Passwordless (Recommended)](#tab/passwordless)
182180
@@ -361,7 +359,7 @@ npm install @azure/eventhubs-checkpointstore-blob
361359
> [!NOTE]
362360
> For the complete source code, including additional informational comments, go to the [GitHub receiveEventsUsingCheckpointStore.js page](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/eventhub/eventhubs-checkpointstore-blob/samples/v1/javascript/receiveEventsUsingCheckpointStore.js).
363361
364-
You have now received events from your event hub. The receiver program receives events from all the partitions of the default consumer group in the event hub.
362+
The receiver program receives events from all the partitions of the default consumer group in the event hub.
365363
366364
## Clean up resources
367365
Delete the resource group that has the Event Hubs namespace or delete only the namespace if you want to keep the resource group.

0 commit comments

Comments
 (0)