Merge pull request #101935 from sethmanheim/jwar

Fix merge conflict in PR #97802

Author: v-shils

articles/notification-hubs/notification-hubs-tags-segment-push-message.md

@@ -16,7 +16,7 @@ ms.topic: article
 ms.date: 12/09/2019
 ms.author: sethm
 ms.reviewer: jowargo
-ms.lastreviewed: 01/23/2019
+ms.lastreviewed: 12/04/2019
 ---
 
 # Routing and tag expressions
@@ -27,19 +27,19 @@ Tag expressions enable you to target specific sets of devices, or more specifica
 
 ## Targeting specific registrations
 
-The only way to target specific notification registrations is to associate tags with them, then target those tags. As discussed in [Registration Management](notification-hubs-push-notification-registration-management.md), in order to receive push notifications an app has to register a device handle on a notification hub. Once a registration is created on a notification hub, the application backend can send push notifications to it. The application backend can choose the registrations to target with a specific notification in the following ways:
+The only way to target specific notification registrations is to associate tags with them, then target those tags. As discussed in [Registration Management](notification-hubs-push-notification-registration-management.md), to receive push notifications, an app must register a device handle on a notification hub. Once the app creates a registration on a notification hub, the application backend can send push notifications to it. The application backend can choose the registrations to target with a specific notification in the following ways:
 
 1. **Broadcast**: all registrations in the notification hub receive the notification.
 2. **Tag**: all registrations that contain the specified tag receive the notification.
 3. **Tag expression**: all registrations whose set of tags match the specified expression receive the notification.
 
 ## Tags
 
-A tag can be any string, up to 120 characters, containing alphanumeric and the following non-alphanumeric characters: ‘_’, ‘@’, ‘#’, ‘.’, ‘:’, ‘-’. The following example shows an application from which you can receive toast notifications about specific music groups. In this scenario, a simple way to route notifications is to label registrations with tags that represent the different bands, as in the following picture:
+A tag can be any string, up to 120 characters, containing alphanumeric and the following non-alphanumeric characters: ‘`_`’, ‘`@`’, ‘`#`’, ‘`.`’, ‘`:`’, ‘`-`’. The following example shows an application from which you can receive toast notifications about specific music groups. In this scenario, a simple way to route notifications is to label registrations with tags that represent the different bands, as in the following figure:
 
 ![Tags overview](./media/notification-hubs-tags-segment-push-message/notification-hubs-tags.png)
 
-In this picture, the message tagged **Beatles** reaches only the tablet that registered with the tag **Beatles**.
+In the figure, the message tagged with **Beatles** reaches only the tablet that registered with the tag **Beatles**.
 
 For more information about creating registrations for tags, see [Registration Management](notification-hubs-push-notification-registration-management.md).
 
@@ -59,13 +59,13 @@ toast = @"<toast><visual><binding template=""ToastGeneric""><text id=""1"">" +
 outcome = await Notifications.Instance.Hub.SendWindowsNativeNotificationAsync(toast, "Wailers");
 ```
 
-Tags do not have to be pre-provisioned and can refer to multiple app-specific concepts. For example, users of this example application can comment on bands and want to receive toasts, not only for the comments on their favorite bands, but also for all comments from their friends, regardless of the band on which they are commenting. The following picture shows an example of this scenario:
+Tags must not be pre-provisioned, and can refer to multiple app-specific concepts. For example, users of this example application can comment on bands and want to receive toasts, not only for the comments on their favorite bands, but also for all comments from their friends, regardless of the band on which they are commenting. The following figure highlights an example of this scenario:
 
 ![Tags friends](./media/notification-hubs-tags-segment-push-message/notification-hubs-tags2.png)
 
-In this picture, Alice is interested in updates for the Beatles, and Bob is interested in updates for the Wailers. Bob is also interested in Charlie’s comments, and Charlie is in interested in the Wailers. When a notification is sent for Charlie’s comment on the Beatles, both Alice and Bob receive it.
+In this example, Alice is interested in updates for the Beatles, and Bob is interested in updates for the Wailers. Bob is also interested in Charlie’s comments, and Charlie is interested in the Wailers. When a notification is sent for Charlie’s comment on the Beatles, Notification Hubs sends it to both Alice and Bob.
 
-While you can encode multiple concerns in tags (for example, “band_Beatles” or “follows_Charlie”), tags are simple strings and not properties with values. A registration is matched only on the presence or absence of a specific tag.
+While you can encode multiple concerns in tags (for example, `band_Beatles` or `follows_Charlie`), tags are simple strings and not properties with values. A registration matches only on the presence or absence of a specific tag.
 
 For a full step-by-step tutorial on how to use tags for sending to interest groups, see [Breaking News](notification-hubs-windows-notification-dotnet-push-xplat-segmented-wns.md).
 
@@ -74,15 +74,15 @@ For a full step-by-step tutorial on how to use tags for sending to interest grou
 
 ## Using tags to target users
 
-Another way to use tags is to identify all the devices of a particular user. Registrations can be tagged with a tag that contains a user ID, as in the following picture:
+Another way to use tags is to identify all the devices associated with a particular user. You can tag a Registration with a tag that contains the user ID, as in the following figure:
 
 ![Tag users](./media/notification-hubs-tags-segment-push-message/notification-hubs-tags3.png)
 
-In this picture, the message tagged uid: Alice reaches all registrations tagged "uid:Alice"; hence, all of Alice’s devices.
+In the figure, the message tagged `user_Alice` reaches all devices tagged with `user_Alice`.
 
 ## Tag expressions
 
-There are cases in which a notification has to target a set of registrations that is identified not by a single tag, but by a Boolean expression on tags.
+There are cases where notifications must target a set of registrations identified not by a single tag, but by a Boolean expression using tags.
 
 Consider a sports application that sends a reminder to everyone in Boston about a game between the Red Sox and Cardinals. If the client app registers tags about interest in teams and location, then the notification should be targeted to everyone in Boston who is interested in either the Red Sox or the Cardinals. This condition can be expressed with the following Boolean expression:
 
@@ -92,9 +92,9 @@ Consider a sports application that sends a reminder to everyone in Boston about
 
 ![Tag expressions](./media/notification-hubs-tags-segment-push-message/notification-hubs-tags4.png)
 
-Tag expressions can contain all Boolean operators, such as AND (&&), OR (||), and NOT (!). They can also contain parentheses. Tag expressions are limited to 20 tags if they contain only ORs; otherwise they are limited to 6 tags.
+Tag expressions support common Boolean operators such as `AND` (`&&`), `OR` (`||`), and `NOT` (`!`); they can also contain parentheses. Tag expressions using only `OR` operators can reference 20 tags; otherwise tag expressions are limited to 6 tags.
 
-Here's an example for sending notifications with tag expressions using the SDK.
+Here's an example for sending notifications with tag expressions using the SDK:
 
 ```csharp
 Microsoft.Azure.NotificationHubs.NotificationOutcome outcome = null;