Skip to content

Commit 55594e0

Browse files
authored
Minor fixes
1 parent fefd84b commit 55594e0

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/azure-web-pubsub/quickstarts-livetry.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 05/27/2025
1010

1111
# Use LiveTry to explore Azure Web PubSub capabilities
1212

13-
**LiveTry** is a browser-based tool that helps you use Azure Web PubSub’s real-time messaging featuresno code or local setup required. With just a few clicks, you can create clients, join groups, and send messages using both client-side and server-side APIs.
13+
**LiveTry** is a browser-based tool that helps you use Azure Web PubSub’s real-time messaging featuresno code or local setup required. With just a few clicks, you can create clients, join groups, and send messages using both client-side and server-side APIs.
1414

1515
This guide walks you through two common messaging scenarios in LiveTry, while helping you understand important concepts like **connections**, **groups**, and **messages**.
1616

@@ -27,7 +27,7 @@ You explore two messaging patterns often used in real-time applications:
2727

2828
## Key concepts
2929

30-
Before getting started, here’s a quick refresher on core Azure Web PubSub concepts that you interact with in LiveTry:
30+
Before we get started, here’s a quick refresher on core Azure Web PubSub concepts that you interact with in LiveTry:
3131

3232
- **Hub**: A logical unit used to isolate and organize messaging logic. Clients always connect to a hub. With LiveTry, real traffic goes through the resource. For this tutorial, we recommend specifying a test hub name that doesn’t overlap with your production traffic.
3333
- **Connection**: A persistent WebSocket connection between a client and the Azure Web PubSub service.
@@ -38,7 +38,7 @@ Before getting started, here’s a quick refresher on core Azure Web PubSub conc
3838

3939
## Scenario 1: Send a message to a group from the server
4040

41-
In this scenario, you simulate server-side broadcasting using the `sendToGroup` REST API. This demonstrates how the service routes a message from your backend to all clients in a specified group.
41+
In this scenario, you simulate server-side broadcasting using the `sendToGroup` REST API. This scenario demonstrates how the service routes a message from your backend to all clients in a specified group.
4242

4343
### Steps
4444
1. In the Azure portal, navigate to your Azure Web PubSub resource.
@@ -52,7 +52,7 @@ In this scenario, you simulate server-side broadcasting using the `sendToGroup`
5252
### What you’re learning
5353
You send messages to a group of clients using RESTful APIs. LiveTry demonstrates how server-to-group communication works without needing to deploy a backend. Azure Web PubSub also provides server SDKs for C#, JavaScript, Java, and Python.
5454

55-
Try repeating the steps with multiple clients to visualize message broadcasting in action. LiveTry supports up to five concurrent simulated clients.
55+
To visualize message broadcasting in action, try repeating the steps with multiple clients . LiveTry supports up to five concurrent simulated clients.
5656

5757
---
5858

@@ -62,9 +62,9 @@ In this scenario, you create a client sending a message to other clients in the
6262

6363
### Steps
6464
1. In **LiveTry**, add two or more clients and specify the same value for the `Initial Groups` field.
65-
2. For the client that will send the message, select **Allow client to send to all groups**.
65+
2. For the client that sends the message, select **Allow client to send to all groups**.
6666
3. Switch to that client’s panel, specify the group name, enter a message, and click **Invoke**.
67-
4. The other clients in the group will receive the message in real time.
67+
4. The other clients in the group receive the message in real time.
6868

6969
### What you’re learning
7070
This scenario showcases **client-to-group messaging**, which is ideal in applications where server round-trips introduce unnecessary latency. It's a core part of Web PubSub’s **client publish/subscribe model**.
@@ -82,5 +82,5 @@ This scenario showcases **client-to-group messaging**, which is ideal in applica
8282
## Next steps
8383

8484
- Learn more about [key concepts](./key-concepts.md) in Azure Web PubSub
85-
- Follow the [Quickstart guide](./quickstarts-pubsub-among-clients.md) to build a local sample
85+
- To build a local sample, follow the [Quickstart guide](./quickstarts-pubsub-among-clients.md)
8686
- Explore guides under "How-to guides" for common tasks when developing with Azure Web PubSub

0 commit comments

Comments
 (0)