Update broken links in touched files

Author: alvinashcraft

uwp/monetize/request-ratings-and-reviews.md

@@ -9,17 +9,18 @@ ms.localizationpriority: medium
 # Request ratings and reviews for your app
 
 You can add code to your Universal Windows Platform (UWP) app to programmatically prompt your customers to rate or review your app. There are several ways you can do this:
+
 * You can show a rating and review dialog directly in the context of your app.
 * You can programmatically open the rating and review page for your app in the Microsoft Store.
 
 When you are ready to analyze your ratings and reviews data, you can view the data in Partner Center or use the Microsoft Store analytics API to retrieve this data programmatically.
 
 > [!IMPORTANT]
-> When adding a rating function within your app, all reviews must send the user to the Store's rating mechanisms, regardless of star rating chosen. If you collect feedback or comments from users, it must be clear that it is not related to the app rating or reviews in the Store but is sent directly to the app developer. See the Developer Code of Conduct for more information related to [Fraudulent or Dishonest Activities](/legal/windows/agreements/store-developer-code-of-conduct#3-fraudulent-or-dishonest-activities).
+> When adding a rating function within your app, all reviews must send the user to the Store's rating mechanisms, regardless of star rating chosen. If you collect feedback or comments from users, it must be clear that it is not related to the app rating or reviews in the Store but is sent directly to the app developer. See the Developer Code of Conduct for more information related to [Fraudulent or Dishonest Activities](/windows/apps/publish/store-developer-code-of-conduct#3-fraudulent-or-dishonest-activities).
 
 ## Show a rating and review dialog in your app
 
-To programmatically show a dialog from your app that asks your customer to rate your app and submit a review, call the [RequestRateAndReviewAppAsync](/uwp/api/windows.services.store.storecontext.requestrateandreviewappasync) method in the [Windows.Services.Store](/uwp/api/windows.services.store) namespace. 
+To programmatically show a dialog from your app that asks your customer to rate your app and submit a review, call the [RequestRateAndReviewAppAsync](/uwp/api/windows.services.store.storecontext.requestrateandreviewappasync) method in the [Windows.Services.Store](/uwp/api/windows.services.store) namespace.
 
 > [!IMPORTANT]
 > The request to show the rating and review dialog must be called on the UI thread in your app.

uwp/whats-new/windows-10-build-14393.md

@@ -42,7 +42,7 @@ InkToolbar | [**InkToolbar**](/uwp/api/Windows.UI.Xaml.Controls.InkToolbar) is a
 MAX_PATH limitations removed | MAX_PATH limitations have been removed from common Win32 file and directory APIs. The behavior is opt-in. Details in the **Maximum Path Length Limitation** section of [Naming Files, Paths, and Namespaces](/windows/desktop/FileIO/naming-a-file).
 Camera - Media Frame Reader |The new [**Windows.Media.Capture.Frames**](/uwp/api/Windows.Media.Capture.Frames) namespace provides APIs for reading media frames from one or more available sources, including color, depth, and infrared cameras, audio devices, or even custom frame sources such as those that produce skeletal tracking frames. This feature is designed to be used by apps that perform real-time processing of media frames, such as augmented reality and depth-aware camera apps.
 Media Playback | The recommended way of playing back media in an app is to use the [**MediaPlayer**](/uwp/api/Windows.Media.Playback.MediaPlayer) class, using the lightweight [**MediaPlayerElement**](/uwp/api/Windows.UI.Xaml.Controls.MediaPlayerElement) class to render media in XAML if desired. Improvements to the **MediaPlayer** class include the ability to play audio to a specific endpoint, the introduction of the [**MediaPlaybackSession**](/uwp/api/Windows.Media.Playback.MediaPlaybackSession) class for managing player state, pinch and zoom for video, the ability to render video to a [**Windows.UI.Composition**](/uwp/api/Windows.UI.Composition) surface, and the [**MediaTimelineController**](/uwp/api/Windows.Media.MediaTimelineController) class for synchronizing playback of multiple media players.<br>When opening media items using [**MediaSource**](/uwp/api/Windows.Media.Core.MediaSource), you can now detect media failures due fully or partially unsupported codecs.<br><br>The new [**MediaBreakManager**](/uwp/api/Windows.Media.Playback.MediaBreakManager) class to quickly and easy add media breaks to any [**MediaPlaybackItem**](/uwp/api/Windows.Media.Playback.MediaPlaybackItem) class allows you to easily create, schedule, and manage media breaks such as audio and video ads.<br><br>The **MediaPlayer** class now gets automatic integration into the System Media Transport Controls (SMTC). The new [**MediaPlaybackCommandManager**](/uwp/api/Windows.Media.Playback.MediaPlaybackCommandManager) class allows you to partially or completely override SMTC commands.<br><br>You can now play media in the background using the new one-process model, which is much simpler and easier to implement than the previous two-process model. A new manifest capability lets you tell the system that your app needs to play media in the background, and new app lifecycle events, [**EnteredBackground**](/uwp/api/windows.applicationmodel.core.coreapplication.enteredbackground) and [**LeavingBackground**](/uwp/api/windows.applicationmodel.core.coreapplication.leavingbackground), give you an opportunity to free up unused resources while running in the background.
-Microsoft Edge | Microsoft Edge adds support for the Fetch, Streams, and Beacon APIs. Fetch is the modern day replacement for **XMLHttpRequests**, adding lower level capabilities for requests and responses. Also added is the ability to stream data sources. Streams enables reading chunks of data from sources as opposed to buffering the entire source before being able to read from it. The Beacon API allows for an efficient way to send information such as critical application and measurement information to a server via beacons(one-way requests). The Beacon API is fully asynchronous and does not need to process a request, thus making it a non-blocking request.<br/><br/>For more information on new APIs in Microsoft Edge, check out [What's new](https://developer.microsoft.com/microsoft-edge/platform/documentation/dev-guide) in the Microsoft Edge Developer Guide.  
+Microsoft Edge | Microsoft Edge adds support for the Fetch, Streams, and Beacon APIs. Fetch is the modern day replacement for **XMLHttpRequests**, adding lower level capabilities for requests and responses. Also added is the ability to stream data sources. Streams enables reading chunks of data from sources as opposed to buffering the entire source before being able to read from it. The Beacon API allows for an efficient way to send information such as critical application and measurement information to a server via beacons(one-way requests). The Beacon API is fully asynchronous and does not need to process a request, thus making it a non-blocking request.<br/><br/>For more information on new APIs in Microsoft Edge, check out what's new in the [Microsoft Edge Developer documentation](/microsoft-edge/developer/).  
 New app lifecycle events | Two new events have been added to the [app lifecycle](../launch-resume/app-lifecycle.md?f=255&MSPPError=-2147217396) that make it easy to detect when your app moves in and out of visibility.
 Single Process background activity | Executing background code is much easier and no longer requires creating a background task. You can run code in the background as either a separate process or directly inside the foreground application. See [Background activity with the Single Process Model](https://blogs.windows.com/buildingapps/2016/06/07/background-activity-with-the-single-process-model/#z3OjoTRbQMVX1puj.99) for details.
 Social extensibility and contact card APIs for the People app | Integrate app-based messaging, voice calling, and video calling actions directly to contact cards. Use contact associations to provide social content into the People app's “What’s new” view.