Grammatical changes.

stevemunk · stevemunk · commit 33cf89f53100 · 2023-09-28T12:44:06.000-05:00
diff --git a/articles/azure-maps/migrate-from-google-maps-web-app.md b/articles/azure-maps/migrate-from-google-maps-web-app.md
@@ -29,7 +29,7 @@ Also:
 > [!div class="checklist"]
 > * How to accomplish common mapping tasks using the Azure Maps Web SDK.
 > * Best practices to improve performance and user experience.
-> * Tips on how to make your application using more advanced features available in Azure Maps.
+> * Tips on how to make your application use more advanced features available in Azure Maps.
 
 If migrating an existing web application, check to see if it's using an open-source map control library. Examples of open-source map control library are: Cesium, Leaflet, and OpenLayers. You can still migrate your application, even if it uses an open-source map control library, and you don't want to use the Azure Maps Web SDK. In such case, connect your application to the Azure Maps [Render] services ([road tiles] | [satellite tiles]). The following points detail on how to use Azure Maps in some commonly used open-source map control libraries.
 
@@ -39,7 +39,7 @@ If migrating an existing web application, check to see if it's using an open-sou
 
 If developing using a JavaScript framework, one of the following open-source projects may be useful:
 
-* [ng-azure-maps] - Angular 10 wrapper around Azure maps.
+* [ng-azure-maps] - Angular 10 wrapper around Azure Maps.
 * [AzureMapsControl.Components] - An Azure Maps Blazor component.
 * [Azure Maps React Component] - A react wrapper for the Azure Maps control.
 * [Vue Azure Maps] - An Azure Maps component for Vue application.
@@ -120,15 +120,15 @@ Both SDKs have the same steps to load a map:
 
 **Some key differences**
 
-* Google maps requires an account key to be specified in the script reference of the API. Authentication credentials for Azure Maps are specified as options of the map class. This credential can be a subscription key or Azure Active Directory information.
+* Google Maps requires an account key to be specified in the script reference of the API. Authentication credentials for Azure Maps are specified as options of the map class. This credential can be a subscription key or Azure Active Directory information.
 * Google Maps accepts a callback function in the script reference of the API, which is used to call an initialization function to load the map. With Azure Maps, the onload event of the page should be used.
 * When referencing the `div` element in which the map renders, the `Map` class in Azure Maps only requires the `id` value while Google Maps requires a `HTMLElement` object.
 * Coordinates in Azure Maps are defined as Position objects, which can be specified as a simple number array in the format `[longitude, latitude]`.
 * The zoom level in Azure Maps is one level lower than the zoom level in Google Maps. This discrepancy is because the difference in the sizes of tiling system of the two platforms.
 * Azure Maps doesn't add any navigation controls to the map canvas. So, by default, a map doesn't have zoom buttons and map style buttons. But, there are control options for adding a map style picker, zoom buttons, compass or rotation control, and a pitch control.
 * An event handler is added in Azure Maps to monitor the `ready` event of the map instance. This event fires when the map has finished loading the WebGL context and all the needed resources. Add any code you want to run after the map completes loading, to this event handler.
 
-The basic examples below uses Google Maps to load a map centered over New York at coordinates. The longitude: -73.985, latitude: 40.747, and the map is at zoom level of 12.
+The following examples use Google Maps to load a map centered over New York at coordinates. The longitude: -73.985, latitude: 40.747, and the map is at zoom level of 12.
 
 #### Before: Google Maps
 
@@ -227,7 +227,7 @@ Running this code in a browser displays a map that looks like the following imag
 For more information on how to set up and use the Azure Maps map control in a web app, see [Use the Azure Maps map control].
 
 > [!NOTE]
-> Unlike Google Maps, Azure Maps does not require an initial center and a zoom level to load the map. If this information is not provided when loading the map, Azure maps will try to determine city of the user. It will center and zoom the map there.
+> Unlike Google Maps, Azure Maps does not require an initial center and a zoom level to load the map. If this information is not provided when loading the map, Azure Maps will try to determine city of the user. It will center and zoom the map there.
 
 **More resources:**
 
@@ -796,7 +796,7 @@ map.events.add('click', marker, function () {
 
 Google Maps supports loading and dynamically styling GeoJSON data via the `google.maps.Data` class. The functionality of this class aligns more with the data-driven styling of Azure Maps. But, there's a key difference. With Google Maps, you specify a callback function. The business logic for styling each feature it processed individually in the UI thread. But in Azure Maps, layers support specifying data-driven expressions as styling options. These expressions are processed at render time on a separate thread. The Azure Maps approach improves rendering performance. This advantage is noticed when larger data sets need to be rendered quickly.
 
-The following examples load a GeoJSON feed of all earthquakes over the last seven days from the USGS. Earthquakes data renders as scaled circles on the map. The color and scale of each circle is based on the magnitude of each earthquake, which is stored in the `"mag"` property of each feature in the data set. If the magnitude is greater than or equal to five, the circle is red. If it's greater or equal to three, but less than five, the circle is orange. If it's less than three, the circle is green. The radius of each circle will be the exponential of the magnitude multiplied by 0.1.
+The following examples load a GeoJSON feed of all earthquakes over the last seven days from the USGS. Earthquakes data renders as scaled circles on the map. The color and scale of each circle is based on the magnitude of each earthquake, which is stored in the `"mag"` property of each feature in the data set. If the magnitude is greater than or equal to five, the circle is red. If it's greater or equal to three, but less than five, the circle is orange. If it's less than three, the circle is green. The radius of each circle is the exponential of the magnitude multiplied by 0.1.
 
 #### Before: Google Maps
 
@@ -957,7 +957,7 @@ GeoJSON is the base data type in Azure Maps. Import it into a data source using
 
 ### Marker clustering
 
-When visualizing many data points on the map, points may overlap each other. Overlapping makes the map looks cluttered, and the map becomes difficult to read and use. Clustering point data is the process of combining data points that are near each other and representing them on the map as a single clustered data point. As the user zooms into the map, the clusters break apart into their individual data points. Cluster data points to improve user experience and map performance.
+When visualizing many data points on the map, points may overlap each other. Overlapping makes the map look cluttered, and the map becomes difficult to read and use. Clustering point data is the process of combining data points that are near each other and representing them on the map as a single clustered data point. As the user zooms into the map, the clusters break apart into their individual data points. Cluster data points to improve user experience and map performance.
 
 In the following examples, the code loads a GeoJSON feed of earthquake data from the past week and adds it to the map. Clusters are rendered as scaled and colored circles. The scale and color of the circles depends on the number of points they contain.
 
@@ -1351,7 +1351,7 @@ map.layers.add(new atlas.layer.TileLayer({
 
 ### Show traffic data
 
-Traffic data can be overlaid both Azure and Google maps.
+Traffic data can be overlaid both Azure and Google Maps.
 
 #### Before: Google Maps
 
@@ -1390,7 +1390,7 @@ If you select one of the traffic icons in Azure Maps, more information is displa
 
 ### Add a ground overlay
 
-Both Azure and Google maps support overlaying georeferenced images on the map. Georeferenced images move and scale as you pan and zoom the map. In Google Maps, georeferenced images are known as ground overlays while in Azure Maps they're referred to as image layers. They're great for building floor plans, overlaying old maps, or imagery from a drone.
+Both Azure and Google Maps support overlaying georeferenced images on the map. Georeferenced images move and scale as you pan and zoom the map. In Google Maps, georeferenced images are known as ground overlays while in Azure Maps they're referred to as image layers. They're great for building floor plans, overlaying old maps, or imagery from a drone.
 
 #### Before: Google Maps
 
@@ -1509,7 +1509,7 @@ Use the `atlas.layer.ImageLayer` class to overlay georeferenced images. This cla
 
 ### Add KML data to the map
 
-Both Azure and Google maps can import and render KML, KMZ and GeoRSS data on the map. Azure Maps also supports GPX, GML, spatial CSV files, GeoJSON, Well Known Text (WKT), Web-Mapping Services (WMS), Web-Mapping Tile Services (WMTS), and Web Feature Services (WFS). Azure Maps reads the files locally into memory and in most cases can handle larger KML files.
+Both Azure and Google Maps can import and render KML, KMZ and GeoRSS data on the map. Azure Maps also supports GPX, GML, spatial CSV files, GeoJSON, Well Known Text (WKT), Web-Mapping Services (WMS), Web-Mapping Tile Services (WMTS), and Web Feature Services (WFS). Azure Maps reads the files locally into memory and in most cases can handle larger KML files.
 
 #### Before: Google Maps
 
diff --git a/articles/azure-maps/migrate-from-google-maps-web-services.md b/articles/azure-maps/migrate-from-google-maps-web-services.md
@@ -3,7 +3,7 @@ title: 'Tutorial - Migrate web services from Google Maps | Microsoft Azure Maps'
 description: Tutorial on how to migrate web services from Google Maps to Microsoft Azure Maps
 author: eriklindeman
 ms.author: eriklind
-ms.date: 06/23/2021
+ms.date: 09/28/2023
 ms.topic: tutorial
 ms.service: azure-maps
 services: azure-maps
@@ -36,21 +36,21 @@ The table shows the Azure Maps service APIs, which have a similar functionality
 | Google Maps service API | Azure Maps service API                         |
 |-------------------------|------------------------------------------------|
 | Directions              | [Route]                                        |
-| Distance Matrix         | [Post Route Matrix]                                 |
+| Distance Matrix         | [Post Route Matrix]                            |
 | Geocoding               | [Search]                                       |
 | Places Search           | [Search]                                       |
 | Place Autocomplete      | [Search]                                       |
 | Snap to Road            | See [Calculate routes and directions] section. |
 | Speed Limits            | See [Reverse geocode a coordinate] section.    |
 | Static Map              | [Render]                                       |
-| Time Zone               | [Timezone]                                    |
+| Time Zone               | [Timezone]                                     |
 
 The following service APIs aren't currently available in Azure Maps:
 
 * Geolocation - Azure Maps does have a service called Geolocation, but it provides IP Address to location information, but doesn't currently support cell tower or WiFi triangulation.
 * Places details and photos - Phone numbers and website URL are available in the Azure Maps search API.
 * Map URLs
-* Nearest Roads - This is achievable using the Web SDK as demonstrated in the [Basic snap to road logic] sample, but is not currently available as a service.
+* Nearest Roads - Achievable using the Web SDK as demonstrated in the [Basic snap to road logic] sample, but isn't currently available as a service.
 * Static street view
 
 Azure Maps has several other REST web services that may be of interest:
@@ -192,7 +192,7 @@ Calculate routes and directions using Azure Maps. Azure Maps has many of the sam
 
 * Arrival and departure times.
 * Real-time and predictive based traffic routes.
-* Different modes of transportation. Such as, driving, walking, bicycling.
+* Different modes of transportation. Such as driving, walking and bicycling.
 
 > [!NOTE]
 > Azure Maps requires all waypoints to be coordinates. Addresses must be geocoded first.
@@ -224,17 +224,17 @@ The table cross-references the Google Maps API parameters with the comparable AP
 > [!TIP]
 > By default, the Azure Maps route API only returns a summary. It returns the distance and times and the coordinates for the route path. Use the `instructionsType` parameter to retrieve turn-by-turn instructions. And, use the `routeRepresentation` parameter to filter out the summary and route path.
 
-Azure Maps routing API has other features that aren't available in Google Maps. When migrating your app, consider using these features, you might find them useful.
+Azure Maps routing API has other features that aren't available in Google Maps. When migrating your app, consider using these features:
 
 * Support for route type: shortest, fastest, trilling, and most fuel efficient.
-* Support for other travel modes: bus, motorcycle, taxi, truck, and van.
+* Support for other travel modes: bus, motorcycle, taxi, truck and van.
 * Support for 150 waypoints.
 * Compute multiple travel times in a single request; historic traffic, live traffic, no traffic.
 * Avoid other road types: carpool roads, unpaved roads, already used roads.
 * Specify custom areas to avoid.
-* Limit the elevation, which the route may ascend.
-* Route based on engine specifications. Calculate routes for combustion or electric vehicles based on engine specifications, and the remaining fuel or charge.
-* Support commercial vehicle route parameters. Such as, vehicle dimensions, weight, number of axels, and cargo type.
+* Limit the elevation that the route may ascend.
+* Route based on engine specifications. Calculate routes for combustion or electric vehicles based on engine specifications and the remaining fuel or charge.
+* Support commercial vehicle route parameters. Such as vehicle dimensions, weight, number of axels and cargo type.
 * Specify maximum vehicle speed.
 
 In addition, the route service in Azure Maps supports [Get Route Range]. Calculating routable ranges is also known as isochrones. It entails generating a polygon covering an area that can be traveled to in any direction from an origin point. All under a specified amount of time or amount of fuel or charge.
@@ -256,10 +256,10 @@ The table cross-references the Google Maps API parameters with the comparable AP
 | `format`  | `format` – specified as part of URL path. Currently only PNG supported. |
 | `key`     | `subscription-key` – For more information, see [Authentication with Azure Maps]. |
 | `language`| `language` – For more information, see [Localization support in Azure Maps].  |
-| `maptype` | `layer` and `style` – See [Supported map styles] documentation. |
+| `maptype` | `layer` and `style` – For more information, see [Supported map styles]. |
 | `markers` | `pins`        |
 | `path`    | `path`        |
-| `region`  | *N/A* – This is a geocoding related feature. Use the `countrySet` parameter when using the Azure Maps geocoding API.  |
+| `region`  | *N/A* – A geocoding related feature. Use the `countrySet` parameter when using the Azure Maps geocoding API.  |
 | `scale`   | *N/A*         |
 | `size`    | `width` and `height` – Max size is 8192 x 8192. |
 | `style`   | *N/A*         |
@@ -271,7 +271,7 @@ The table cross-references the Google Maps API parameters with the comparable AP
 
 For more information, see [Render custom data on a raster map].
 
-In addition to being able to generate a static map image, the Azure Maps render service provides the ability to directly access map tiles in raster (PNG) and vector format:
+In addition to being able to generate a static map image, the Azure Maps render service enables direct access of map tiles in raster (PNG) and vector format:
 
 * [Get Map Static Image]: Retrieve raster (PNG) and vector tiles for the base maps (roads, boundaries, background).
 * [Get Map Tile]: Retrieve aerial and satellite imagery tiles.
@@ -364,7 +364,7 @@ Add three pins with the label values '1', '2', and '3':
 
 **Before: Google Maps**
 
-Add lines and polygon to a static map image using the `path` parameter in the URL. The `path` parameter takes in a style and a list of locations to be rendered on the map, as shown below:
+Add lines and polygon to a static map image using the `path` parameter in the URL. The `path` parameter takes in a style and a list of locations to be rendered on the map:
 
 ```text
 &path=pathStyles|pathLocation1|pathLocation2|...
@@ -374,7 +374,7 @@ Use other styles by adding extra `path` parameters to the URL with a different s
 
 Path locations are specified with the `latitude1,longitude1|latitude2,longitude2|…` format. Paths can be encoded or contain addresses for points.
 
-Add path styles with the `optionName:value` format, separate multiple styles by the pipe (\|) characters. And, separate option names and values with a colon (:). Like this: `optionName1:value1|optionName2:value2`. The following style option names can be used to style paths in Google Maps:
+Add path styles with the `optionName:value` format, separate multiple styles by the pipe (\|) characters. Also separate option names and values with a colon (:). For example: `optionName1:value1|optionName2:value2`. The following style option names can be used to style paths in Google Maps:
 
 * `color` – The color of the path or polygon outline. Can be a 24-bit hex color (`0xrrggbb`), a 32-bit hex color (`0xrrggbbbaa`) or one of the following values: black, brown, green, purple, yellow, blue, gray, orange, red, white.
 * `fillColor` – The color to fill the path area with (polygon). Can be a 24-bit hex color (`0xrrggbb`), a 32-bit hex color (`0xrrggbbbaa`) or one of the following values: black, brown, green, purple, yellow, blue, gray, orange, red, white.
