Skip to content

Commit 4ad9c04

Browse files
committed
Acrolinx
1 parent 70643dc commit 4ad9c04

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/notification-hubs/notification-hubs-push-notification-registration-management.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Device registration with a Notification Hub is accomplished using a **Registrati
2929

3030
### Registrations
3131

32-
A registration associates the Platform Notification Service (PNS) handle for a device with tags and possibly a template. The PNS handle could be a ChannelURI, device token, or FCM registration id. Tags are used to route notifications to the correct set of device handles. For more information, see [Routing and Tag Expressions](notification-hubs-tags-segment-push-message.md). Templates are used to implement per-registration transformation. For more information, see [Templates](notification-hubs-templates-cross-platform-push-messages.md).
32+
A registration associates the Platform Notification Service (PNS) handle for a device with tags and possibly a template. The PNS handle could be a ChannelURI, device token, or FCM registration ID. Tags are used to route notifications to the correct set of device handles. For more information, see [Routing and Tag Expressions](notification-hubs-tags-segment-push-message.md). Templates are used to implement per-registration transformation. For more information, see [Templates](notification-hubs-templates-cross-platform-push-messages.md).
3333

3434
> [!NOTE]
3535
> Azure Notification Hubs supports a maximum of 60 tags per device.
@@ -166,7 +166,7 @@ var channel = await PushNotificationChannelManager.CreatePushNotificationChannel
166166
string installationId = null;
167167
var settings = ApplicationData.Current.LocalSettings.Values;
168168

169-
// If we have not stored an installation id in application data, create and store as application data.
169+
// If we have not stored an installation ID in application data, create and store as application data.
170170
if (!settings.ContainsKey("__NHInstallationId"))
171171
{
172172
installationId = Guid.NewGuid().ToString();
@@ -208,15 +208,15 @@ These methods create or update a registration for the device on which they are c
208208
// Initialize the Notification Hub
209209
NotificationHubClient hub = NotificationHubClient.CreateClientFromConnectionString(listenConnString, hubName);
210210

211-
// The Device id from the PNS
211+
// The Device ID from the PNS
212212
var pushChannel = await PushNotificationChannelManager.CreatePushNotificationChannelForApplicationAsync();
213213

214-
// If you are registering from the client itself, then store this registration id in device
215-
// storage. Then when the app starts, you can check if a registration id already exists or not before
214+
// If you are registering from the client itself, then store this registration ID in device
215+
// storage. Then when the app starts, you can check if a registration ID already exists or not before
216216
// creating.
217217
var settings = ApplicationData.Current.LocalSettings.Values;
218218

219-
// If we have not stored a registration id in application data, store in application data.
219+
// If we have not stored a registration ID in application data, store in application data.
220220
if (!settings.ContainsKey("__NHRegistrationId"))
221221
{
222222
// make sure there are no existing registrations for this push handle (used for iOS and Android)
@@ -324,7 +324,7 @@ var reg = new WindowsRegistrationDescription(channelUri, tags);
324324
// Create
325325
await hub.CreateRegistrationAsync(reg);
326326

327-
// Get by id
327+
// Get by ID
328328
var r = await hub.GetRegistrationAsync<RegistrationDescription>("id");
329329

330330
// update

0 commit comments

Comments
 (0)