Merge pull request #96566 from craigktreasure/craig/seo-titles

Updated Spatial Anchors titles for SEO

Author: GitHubber17

articles/spatial-anchors/concepts/anchor-relationships-way-finding.md

@@ -1,8 +1,8 @@
 ---
-title: Anchor relationships and way-finding in Azure Spatial Anchors | Microsoft Docs
-description: Learn about the conceptual model behind anchor relationships. Learn to connect anchors within a space and to use the Nearby API to fulfill a way-finding scenario. 
+title: Anchor relationships and way-finding
+description: Learn about the conceptual model behind anchor relationships. Learn to connect anchors within a space and to use the Nearby API to fulfill a way-finding scenario.
 author: ramonarguelles
-manager: vicenterivera
+manager: vriveras
 services: azure-spatial-anchors
 
 ms.author: rgarcia
@@ -55,11 +55,11 @@ To connect anchors:
 
 ### Connect anchors in multiple sessions
 
-You can connect spatial anchors over multiple sessions. Using this method, you can create and connect some anchors at one time and then later create and connect more anchors. 
+You can connect spatial anchors over multiple sessions. Using this method, you can create and connect some anchors at one time and then later create and connect more anchors.
 
 To connect anchors over multiple sessions:
 
-1. The app creates some anchors in one CloudSpatialAnchorSession. 
+1. The app creates some anchors in one CloudSpatialAnchorSession.
 2. At a different time, the app locates one of these anchors (for example, Anchor A) by using a new CloudSpatialAnchorSession.
 3. Walk to a new location. The underlying mixed-reality or augmented-reality platform tracks the movement.
 4. Create Anchor C by using the same CloudSpatialAnchorSession. Anchors A, B, and C are now connected. The Spatial Anchors service maintains this relationship.
@@ -68,7 +68,7 @@ You can continue this procedure for more anchors and more sessions over time.
 
 ### Verify anchor connections
 
-The app can verify that two anchors are connected by issuing a query for nearby anchors. When the query's result contains the target anchor, the anchor connection is verified. If the anchors aren't connected, the app can try to connect them again. 
+The app can verify that two anchors are connected by issuing a query for nearby anchors. When the query's result contains the target anchor, the anchor connection is verified. If the anchors aren't connected, the app can try to connect them again.
 
 Here are some reasons why anchors might fail to connect:
 

articles/spatial-anchors/concepts/authentication.md

@@ -1,6 +1,6 @@
 ---
-title: Authentication and authorization to Azure Spatial Anchors | Microsoft Docs
-description: Learn about the various ways an app or service can authenticate to Azure Spatial Anchors, and the levels of control that you have to gate access to Azure Spatial Anchors.  
+title: Authentication and authorization
+description: Learn about the various ways an app or service can authenticate to Azure Spatial Anchors, and the levels of control that you have to gate access to Azure Spatial Anchors.
 author: julianparismorgan
 manager: vriveras
 services: azure-spatial-anchors
@@ -12,22 +12,22 @@ ms.service: azure-spatial-anchors
 ---
 # Authentication and authorization to Azure Spatial Anchors
 
-In this section, we will cover the various ways you can authenticate to Azure Spatial Anchors from your app or web service, and the ways in which you can use Role-Based Access Control in Azure Directory (Azure AD) to control access to your Spatial Anchors accounts.  
+In this section, we will cover the various ways you can authenticate to Azure Spatial Anchors from your app or web service, and the ways in which you can use Role-Based Access Control in Azure Directory (Azure AD) to control access to your Spatial Anchors accounts.
 
 ## Overview
 
 ![An overview of authentication to Azure Spatial Anchors](./media/spatial-anchors-authentication-overview.png)
 
-To access a given Azure Spatial Anchors account, clients need to first obtain an access token from Azure Mixed Reality Security Token Service (STS). Tokens obtained from STS live for 24 hours, and contain information for the Spatial Anchors services to make authorization decisions on the account, and ensure that only authorized principals can access that account. 
+To access a given Azure Spatial Anchors account, clients need to first obtain an access token from Azure Mixed Reality Security Token Service (STS). Tokens obtained from STS live for 24 hours, and contain information for the Spatial Anchors services to make authorization decisions on the account, and ensure that only authorized principals can access that account.
 
-Access tokens can be obtained in exchange from either account keys, or from Azure AD-issued tokens. 
+Access tokens can be obtained in exchange from either account keys, or from Azure AD-issued tokens.
 
-Account keys enable you to get quickly started on using the Azure Spatial Anchors service; however, before you deploy your application to production, it is advised that you update your app to use Azure AD-based authentication. 
+Account keys enable you to get quickly started on using the Azure Spatial Anchors service; however, before you deploy your application to production, it is advised that you update your app to use Azure AD-based authentication.
 
 Azure AD authentication tokens can be obtained two ways:
 
-- If you are building an enterprise application, and your company is using Azure AD as its identity system, you may use user-based Azure AD authentication in your app, and grant access to your spatial anchors accounts using your existing Azure AD security groups, or directly to users in your organization. 
-- Otherwise, it is recommended that you obtain Azure AD tokens from a web service supporting your app. Using a supporting web service is the recommended method of authentication for production applications, as it avoids embedding the credentials for accessing Azure Spatial Anchors in your client application. 
+- If you are building an enterprise application, and your company is using Azure AD as its identity system, you may use user-based Azure AD authentication in your app, and grant access to your spatial anchors accounts using your existing Azure AD security groups, or directly to users in your organization.
+- Otherwise, it is recommended that you obtain Azure AD tokens from a web service supporting your app. Using a supporting web service is the recommended method of authentication for production applications, as it avoids embedding the credentials for accessing Azure Spatial Anchors in your client application.
 
 ## Account keys
 
@@ -36,9 +36,9 @@ Using account keys for access to your Azure Spatial Anchors account is the simpl
 ![An overview of authentication to Azure Spatial Anchors](../../../includes/media/spatial-anchors-get-started-create-resource/view-account-key.png)
 
 
-Two keys are made available, which are both simultaneously valid for access to the Spatial Anchors account. It is recommended that you regularly update the key you use to access the account; having two separate valid keys enable such updates without downtime; you only have to update  alternatively the primary key and the secondary key. 
+Two keys are made available, which are both simultaneously valid for access to the Spatial Anchors account. It is recommended that you regularly update the key you use to access the account; having two separate valid keys enable such updates without downtime; you only have to update  alternatively the primary key and the secondary key.
 
-The SDK has built-in support for authenticating with account keys; you simply need to set the AccountKey property on your cloudSession object. 
+The SDK has built-in support for authenticating with account keys; you simply need to set the AccountKey property on your cloudSession object.
 
 # [C#](#tab/csharp)
 
@@ -80,33 +80,33 @@ configuration.AccountKey(LR"(MyAccountKey)");
 
 ---
 
-Once that is done, the SDK will handle the exchange of the account key for an access token, and the necessary caching of tokens for your app. 
+Once that is done, the SDK will handle the exchange of the account key for an access token, and the necessary caching of tokens for your app.
 
-> [!WARNING] 
+> [!WARNING]
 > Use of account keys is recommended for quick on-boarding, but during development/prototyping only. It is strongly recommended not to ship your application to production using an embedded account key in it, and to instead use the user-based or service-based Azure AD authentication approaches listed next.
 
 ## Azure AD user authentication
 
 For applications targeting Azure Active Directory users, the recommended approach is to use an Azure AD token for the user, which you can obtain using the ADAL library as described in the following documentation: [https://docs.microsoft.com/azure/active-directory/develop/v1-overview](../../active-directory/develop/v1-overview.md); you should follow the steps listed under “Quick starts”, which include:
 
 1. Configuration in Azure portal
-    1.	Register your application in Azure AD as **Native application**. As part of registering, you will need to determine whether your application should be multi-tenant or not, and provide the redirect URLs allowed for your application.  
-    2.	Grant your application or users access to your resource: 
+    1.	Register your application in Azure AD as **Native application**. As part of registering, you will need to determine whether your application should be multi-tenant or not, and provide the redirect URLs allowed for your application.
+    2.	Grant your application or users access to your resource:
         1.	Navigate to your Spatial Anchors resource in Azure portal
         2.	Switch to the **Access control (IAM)** tab
         3.	Hit **Add role assignment**
             1.	[Select a role](#role-based-access-control)
-            2.	In the **Select** field, enter the name of the user(s), group(s), and/or application(s) to which you want to assign access. 
+            2.	In the **Select** field, enter the name of the user(s), group(s), and/or application(s) to which you want to assign access.
             3.	Hit **Save**.
 2. In your code:
     1.	Make sure to use the **application ID** and **redirect Uri** of your own Azure AD application as the **client ID** and **RedirectUri** parameters in ADAL
     2.	Set the tenant information:
         1.	If your application supports **My organization only**, replace this value with your **Tenant ID** or **Tenant name** (for example, contoso.microsoft.com)
         2.	If your application supports **Accounts in any organizational directory**, replace this value with **Organizations**
         3.	If your application supports **All Microsoft account users**, replace this value with **Common**
-    3.	On your token request, set the **resource** to "https://sts.mixedreality.azure.com". This "resource" will indicate to Azure AD that your application is requesting a token for the Azure Spatial Anchors service.  
+    3.	On your token request, set the **resource** to "https://sts.mixedreality.azure.com". This "resource" will indicate to Azure AD that your application is requesting a token for the Azure Spatial Anchors service.
 
-With that, your application should be able to obtain from ADAL an Azure AD token; you can set that Azure AD token as the **authenticationToken** on your cloud session config object. 
+With that, your application should be able to obtain from ADAL an Azure AD token; you can set that Azure AD token as the **authenticationToken** on your cloud session config object.
 
 # [C#](#tab/csharp)
 
@@ -169,12 +169,12 @@ The Azure AD access token is retrieved using the ADAL library as described in th
         2.	Switch to the **Access control (IAM)** tab
         3.	Hit **Add role assignment**
         1.	[Select a role](#role-based-access-control)
-        2.	In the **select** field, enter the name of the application(s) you created and to which you want to assign access. If you want your app’s users to have different roles against the Spatial Anchors account, you should register multiple applications in Azure AD, and assign to each a separate role. Then implement your authorization logic to use the right role for your users.  
+        2.	In the **select** field, enter the name of the application(s) you created and to which you want to assign access. If you want your app’s users to have different roles against the Spatial Anchors account, you should register multiple applications in Azure AD, and assign to each a separate role. Then implement your authorization logic to use the right role for your users.
     3.	Hit **Save**.
 2.	In your code (note: you can use the service sample included on GitHub):
     1.	Make sure to use the application ID, application secret, and redirect Uri of your own Azure AD application as the client ID, secret, and RedirectUri parameters in ADAL
     2.	Set the tenant ID to your own AAAzure ADD tenant ID in the authority parameter in ADAL
-    3.	On your token request, set the **resource** to "https://sts.mixedreality.azure.com" 
+    3.	On your token request, set the **resource** to "https://sts.mixedreality.azure.com"
 
 With that, your backend service can retrieve an Azure AD token. It can then exchange it for an MR token that it will return back to the client. Using an Azure AD token to retrieve an MR token is done via a REST call. Here is a sample call:
 
@@ -196,7 +196,7 @@ MS-CV: 05JLqWeKFkWpbdY944yl7A.0
 Where the Authorization header is formatted as follows: `Bearer <accoundId>:<accountKey>`
 
 And the response contains the MR token in plain text.
- 
+
 That MR token is then returned to the client. Your client app can then set it as its access token in the cloud session config.
 
 # [C#](#tab/csharp)
@@ -243,8 +243,8 @@ configuration.AccessToken(LR"(MyAccessToken)");
 
 To help control the level of access granted to applications, services or Azure AD users of your service, the following roles have been created for you to assign as needed against your Azure Spatial Anchors accounts:
 
-- **Spatial Anchors Account Owner**: applications or users that have this role are able to create spatial anchors, query for them, and delete them. When you authenticate to your account using account keys, the **Spatial Anchors Account Owner** role is assigned to the authenticated principal. 
-- **Spatial Anchors Account Contributor**: applications or users that have this role are able to create spatial anchors, query for them, but cannot delete them. 
+- **Spatial Anchors Account Owner**: applications or users that have this role are able to create spatial anchors, query for them, and delete them. When you authenticate to your account using account keys, the **Spatial Anchors Account Owner** role is assigned to the authenticated principal.
+- **Spatial Anchors Account Contributor**: applications or users that have this role are able to create spatial anchors, query for them, but cannot delete them.
 - **Spatial Anchors Account Reader**: applications or users that have this role are only able to query for spatial anchors, but cannot create new ones, delete existing ones, or update metadata on spatial anchors. This is typically used for applications where some users curate the environment, while others can only recall anchors previously placed in that environment.
 
 ## Next steps

articles/spatial-anchors/concepts/coarse-reloc.md

@@ -1,5 +1,5 @@
 ---
-title: Coarse Relocalization | Microsoft Docs
+title: Coarse Relocalization
 description: Coarse relocalization quickstart guide.
 author: bucurb
 manager: dacoghl

articles/spatial-anchors/concepts/guidelines-effective-anchor-experiences.md

@@ -1,5 +1,5 @@
 ---
-title: Guidelines for effective anchor experiences that use Azure Spatial Anchors | Microsoft Docs
+title: Guidelines for effective anchor experiences
 description: Guidelines and considerations to create and locate anchors effectively by using Azure Spatial Anchors.
 author: mattwojo
 manager: jken
@@ -36,7 +36,7 @@ For dynamic locations, you should think about how you teach or guide users in yo
 
 ## Stable visual features
 
-Visual tracking systems used on mixed-reality and augmented-reality devices rely on visual features of the environment. To get the most reliable experience:  
+Visual tracking systems used on mixed-reality and augmented-reality devices rely on visual features of the environment. To get the most reliable experience:
 
 - *Do* create anchors in locations that have stable visual features (that is, features that don't change often).
 
@@ -58,9 +58,9 @@ In general, when creating an anchor, scan it from the perspectives of the people
 
 ## Multiple anchors
 
-Lighting can make a difference in the visual features that an app detects. Anchors created in strong natural light might be hard to locate in artificial light, and vice versa.  
+Lighting can make a difference in the visual features that an app detects. Anchors created in strong natural light might be hard to locate in artificial light, and vice versa.
 
-If you have this issue, it can help to create two anchors. At the same spot, create one anchor in the daylight and another in artificial light. Your app can then query for both anchors. When either anchor is located, the app will have a pose for the anchor. 
+If you have this issue, it can help to create two anchors. At the same spot, create one anchor in the daylight and another in artificial light. Your app can then query for both anchors. When either anchor is located, the app will have a pose for the anchor.
 
 Similarly, in environments where the visual features change because most objects move, multiple anchors can help. When an anchor becomes too difficult to find because of significant changes in the environment, you can replace the anchor with a new one. You might do this, for example, in a retail store where the layout is refreshed every few months.
 
@@ -70,7 +70,7 @@ In many cases, an anchor is an entry point to your app's experience. You'll want
 
 ### Targets
 
-In the target scenario, the location of an anchor is well known. For example, in a fictional mixed-reality painting app, one user places a virtual canvas on the wall. She instructs the other users in the room to point their devices at the same place on the wall to locate the anchor and begin the experience.  
+In the target scenario, the location of an anchor is well known. For example, in a fictional mixed-reality painting app, one user places a virtual canvas on the wall. She instructs the other users in the room to point their devices at the same place on the wall to locate the anchor and begin the experience.
 
 Another example of a target scenario might be a sign in a coffee shop that reads, “Scan for deals.” The coffee shop has placed an anchor here. As users scan the sign, they locate the anchor and enter the augmented-reality experience to find deals on coffee.
 
@@ -100,7 +100,7 @@ First, if the user doesn't locate an anchor within a few seconds, the app should
 
 For target scenarios, ask the user to move around the target to view it from different perspectives. In other words, ask the user to capture the target from new perspectives until the anchor is located.
 
-For room scenarios, ask the user to slowly scan the room. For example, ask the user to turn to capture 180 degrees or even 360 degrees of the room. Or ask the user to view the room from a new perspective. 
+For room scenarios, ask the user to slowly scan the room. For example, ask the user to turn to capture 180 degrees or even 360 degrees of the room. Or ask the user to view the room from a new perspective.
 
 The most meaningful method is to scan across the room. A scan across the room captures more visual features of the environment than a scan of a nearby wall, for example. A scan of a nearby wall won't capture as many useful visual features of the environment.