fixed links

Author: stevemunk

articles/azure-maps/how-to-create-data-registries.md

@@ -16,8 +16,8 @@ The [data registry] service enables you to register data content in an Azure Sto
 
 ## Prerequisites
 
-- [Azure Maps account]
-- [Subscription key]
+- An [Azure Maps account]
+- A[Subscription key]
 - An [Azure storage account]
 
 >[!IMPORTANT]
@@ -364,6 +364,7 @@ When you register a file in Azure Maps using the data registry API, an MD5 hash
 [Azure Maps account]: quick-demo-map-app.md#create-an-azure-maps-account
 [Azure Maps service geographic scope]: geographic-scope.md
 [Azure portal]: https://portal.azure.com/
+[Azure storage account]: /azure/storage/common/storage-account-create?tabs=azure-portal
 [AzureBlob]: #the-azureblob
 [blobUrl]: #the-bloburl-property
 [Create a data registry]: #create-a-data-registry

articles/azure-maps/how-to-dataset-geojson.md

@@ -129,7 +129,7 @@ Feature IDs can only contain alpha-numeric (a-z, A-Z, 0-9), hyphen (-), dot (.)
 
 ### Facility ontology 2.0 validations in the Dataset
 
-[Facility ontology] defines how Azure Maps Creator internally stores facility data, divided into feature classes, in a Creator dataset. When importing a GeoJSON package, anytime a feature is added or modified, a series of validations run. This includes referential integrity checks and geometry and attribute validations. These validations are described in more detail in the following list.
+[Facility Ontology 2.0] defines how Azure Maps Creator internally stores facility data, divided into feature classes, in a Creator dataset. When importing a GeoJSON package, anytime a feature is added or modified, a series of validations run. This includes referential integrity checks and geometry and attribute validations. These validations are described in more detail in the following list.
 
 - The maximum number of features that can be imported into a dataset at a time is 150,000.
 - The facility area can be between 4 and 4,000 Sq Km.