Skip to content

Commit 476ce71

Browse files
committed
making grammatical fixes
1 parent ef811d0 commit 476ce71

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/event-hubs/event-hubs-data-explorer.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Operations run on an Azure Event Hubs namespace are of two kinds.
2121
> [!IMPORTANT]
2222
> * The Event Hubs Data Explorer doesn't support **management operations**. The event hub must be created before the data explorer can send or view events from that event hub.
2323
> * While events payloads (known as **values** in Kafka) sent using the **Kafka protocol** will be visible via the data explorer, the **key** for the specific event will not be visible.
24-
> * We advice against using the Event Hubs Data Explorer for larger messages, as this may result in timeouts, depending on the message size, network latency between client and Service Bus service etc. Instead, we recommend that you use your own client to work with larger messages, where you can specify your own timeout values.
24+
> * We advise against using the Event Hubs Data Explorer for larger messages, as this may result in timeouts, depending on the message size, network latency between client and Service Bus service etc. Instead, we recommend that you use your own client to work with larger messages, where you can specify your own timeout values.
2525
>
2626
2727
## Prerequisites
@@ -38,7 +38,7 @@ Either navigate to the `Data Explorer` directly where you can pick the event hub
3838

3939
### Send Events
4040

41-
You can send either custom payloads, or precanned dataset to the selected event hub using the `Send events` experience.
41+
You can send either custom payloads, or precanned datasets to the selected event hub using the `Send events` experience.
4242

4343
To do so, select the `send events` button, which enables the right pane.
4444

@@ -51,9 +51,9 @@ To send a custom payload -
5151
1. **Select Dataset** - Pick `Custom payload`.
5252
2. Select the **Content-Type**, from either `Text/Plain`, `JSON`, or `XML`.
5353
3. Either upload a JSON file, or type out the payload in the **Enter payload** box.
54-
4. [Optional] Specific system properties.
55-
5. [Optional] Custom properties - available in key-value pair.
56-
6. [Optional] If you wish to send multiple payloads, check the **Repeat send** box, and specify the **Repeat send count** (that is, the number of payloads to send) and the **Interval between repeat send in ms**.
54+
4. **[Optional]** Specify system properties.
55+
5. **[Optional]** Specify custom properties - available as key-value pair.
56+
6. **[Optional]** If you wish to send multiple payloads, check the **Repeat send** box, and specify the **Repeat send count** (that is, the number of payloads to send) and the **Interval between repeat send in ms**.
5757

5858
Once the payload details are defined, select **Send** to send the event payload as defined.
5959

@@ -64,9 +64,9 @@ Once the payload details are defined, select **Send** to send the event payload
6464

6565
To send event payloads from a precanned dataset -
6666
1. **Select Dataset** - Pick an option from the **Pre canned datasets**, for example, Yellow taxi, Weather data, and others.
67-
2. [Optional] Specific system properties.
68-
3. [Optional] Custom properties - available in key-value pair.
69-
4. [Optional] If you wish to send multiple payloads, check the **Repeat send** box, and specify the **Repeat send count** (that is, the number of payloads to send) and the **Interval between repeat send in ms**.
67+
2. **[Optional]** Specify system properties.
68+
3. **[Optional]** Specify custom properties - available as key-value pairs.
69+
4. **[Optional]** If you wish to send multiple payloads, check the **Repeat send** box, and specify the **Repeat send count** (that is, the number of payloads to send) and the **Interval between repeat send in ms**.
7070

7171
Once the payload details are defined, select **Send** to send the event payload as defined.
7272

@@ -82,8 +82,8 @@ To view events, you can define the below properties, or rely on the default -
8282
:::image type="content" source="./media/event-hubs-data-explorer/view-event-menu.png" alt-text="Screenshot showing the data explorer menu with view events selected.":::
8383

8484

85-
1. **PartitionID** - pick either a specific partition or select *All partition IDs*.
86-
2. **Consumer Group** - pick the *$Default* or another consumer group, or create one on the fly.
85+
1. **PartitionID** - Pick either a specific partition or select *All partition IDs*.
86+
2. **Consumer Group** - Pick the *$Default* or another consumer group, or create one on the fly.
8787
3. **Event position** - Pick the *oldest position* (that is, the start of the event hub), *Newest position* (that is, latest), *Custom position* (for a specific offset, sequence number or timestamp).
8888
4. **Advanced properties** - Specify the *maximum batch size* and *maximum wait time in seconds*.
8989

0 commit comments

Comments
 (0)