Apply suggestions from code review

Co-authored-by: steve munk <[email protected]>

Author: yulinscottkang

articles/azure-maps/android-sdk-migration-guide.md

@@ -22,7 +22,7 @@ To use the Map Control in a web page, you must have one of the following prerequ
 
 ## Create a WebView
 
-If your Android application doesn't already have a WebView, you need to add one. You can do so by adding the WebView element to your layout XML or programmatically in your Java code. Make sure to set up the WebView to occupy the desired area of your layout.
+Add a `WebView` if your Android application doesn't have one. Do so by adding the `WebView` element to your layout XML or programmatically in your Java code. Be sure it's configured to occupy the desired area of your layout.
 
 ```xml
 <?xml version="1.0" encoding="utf-8"?>
@@ -41,7 +41,7 @@ If your Android application doesn't already have a WebView, you need to add one.
 </androidx.coordinatorlayout.widget.CoordinatorLayout>
 ```
 
-Make sure to include the necessary permissions in your AndroidManifest.xml to enable internet access.
+Enable internet access by adding permissions in AndroidManifest.xml.
 
 ```xml
 <uses-permission android:name="android.permission.INTERNET" />
@@ -144,11 +144,11 @@ To enable communication between your Android application and the WebView, you ca
 
 ## Clean Up Native Map Implementation
 
-Remove the code related to the native Azure Maps Android SDK from your project. This includes dependencies and initialization code related to `com.azure.android:azure-maps-control`.
+Remove code related to the native Azure Maps Android SDK, including dependencies and initialization code related to `com.azure.android:azure-maps-control`.
 
 ## Testing
 
-Test your application thoroughly to ensure that the migration has been successful. Check for any issues related to map functionality, user interactions, and performance.
+Test your application thoroughly to ensure the migration was successful. Check for issues related to map functionality, user interactions, and performance.
 
 ## Next steps
 

articles/azure-maps/ios-sdk-migration-guide.md

@@ -22,7 +22,7 @@ To use the Map Control in a web page, you must have one of the following prerequ
 
 ## Create a WebView
 
-If your iOS application doesn't already have a WebView, you need to add one. You can do so by adding a WKWebView to your storyboard or programmatically in your Swift code. Make sure to set up the WKWebView to occupy the desired area of your view.
+Add a `WebView` if your iOS application doesn't have one. Do so by adding the `WKWebView` to your storyboard or programmatically in your Swift code. Be sure it's configured to occupy the desired area of your layout.
 
 ```swift
 import UIKit
@@ -123,15 +123,15 @@ Save and run the app. A map should be shown within a WebView. Add any features o
 
 ## Communication between native code and WebView (optional)
 
-To enable communication between your iOS application and the WebView, you can use the `WKScriptMessageHandler` protocol provided by the `WKWebView` class. It allows you to establish a bridge for communication between JavaScript running in the WebView and your Swift code. For more information, see the [iOS webkit documentation].
+To enable communication between your iOS application and the WebView, you can use the `WKScriptMessageHandler` protocol provided by the `WKWebView` class. It allows you to establish a bridge for communication between JavaScript running in the WebView and your Swift code. For more information, see [WKScriptMessageHandler] in the iOS webkit documentation.
 
 ## Clean Up Native Map Implementation
 
-Remove the code related to the native Azure Maps iOS SDK from your project. This includes dependencies and initialization code related to `azure-maps-ios-sdk-distribution`.
+Remove code related to the native Azure Maps iOS SDK from your project, including dependencies and initialization code related to `azure-maps-ios-sdk-distribution`.
 
 ## Testing
 
-Test your application thoroughly to ensure that the migration has been successful. Check for any issues related to map functionality, user interactions, and performance.
+Test your application thoroughly to ensure that the migration was successful. Check for issues related to map functionality, user interactions, and performance.
 
 ## Next steps
 
@@ -145,7 +145,7 @@ Learn how to add maps to web and mobile applications using the Map Control clien
 [authentication options]: /javascript/api/azure-maps-control/atlas.authenticationoptions
 [Azure Maps documentation]: how-to-use-map-control.md
 [Azure Maps Code Samples website]: https://samples.azuremaps.com/
-[iOS webkit documentation]: https://developer.apple.com/documentation/webkit/wkscriptmessagehandler
+[WKScriptMessageHandler]: https://developer.apple.com/documentation/webkit/wkscriptmessagehandler
 [Use the Azure Maps map control]: how-to-use-map-control.md
 
 

articles/azure-maps/web-sdk-migration-guide.md

@@ -1,5 +1,5 @@
 ---
-title: The Azure Maps Web SDK v1 and v2 migration guide
+title: The Azure Maps Web SDK migration guide
 titleSuffix: Microsoft Azure Maps
 description: Find out how to migrate your Azure Maps Web SDK v1 and v2 applications to the most recent version of the Web SDK.
 author: sinnypan
@@ -9,7 +9,7 @@ ms.topic: how-to
 ms.service: azure-maps
 ---
 
-# The Azure Maps Web SDK v1 and v2 migration guide
+# The Azure Maps Web SDK migration guide
 
 Thank you for choosing the Azure Maps Web SDK for your mapping needs. This migration guide helps you transition from v1 and v2 to v3, allowing you to take advantage of the latest features and enhancements.
 
@@ -21,7 +21,7 @@ Before you start the migration process, it's important to familiarize yourself w
 
 ### CDN
 
-If you're using CDN ([content delivery network]), update the references to the [v3](#v3) stylesheet and JavaScript within the `head` element of your HTML files.
+If you're using CDN ([content delivery network]), update the references to the [v3](#v3) stylesheet and JavaScript in the `head` element of your HTML files.
 
 #### v1