Merge pull request #3188 from MicrosoftDocs/pehecke-accessibility-updates

phecke · web-flow · commit f593c04273f7 · 2020-07-30T14:38:47.000-07:00
Accessibility updates
diff --git a/powerapps-docs/developer/common-data-service/configure-entities-attributes-auditing.md b/powerapps-docs/developer/common-data-service/configure-entities-attributes-auditing.md
@@ -39,7 +39,7 @@ There are three levels where auditing can be configured: organization, entity, a
   
  The following table lists the non-customizable entities that cannot be audited. This table was obtained by testing for a `CanModifyAuditSettings` attribute value of `false` on each entity’s metadata.  
   
-||  
+|Non-customizable entities|  
 |-|  
 |ActivityPointer|  
 |Annotation|  
diff --git a/powerapps-docs/developer/common-data-service/entity-metadata.md b/powerapps-docs/developer/common-data-service/entity-metadata.md
@@ -177,7 +177,7 @@ Some entities will have different sets of options.
 **Example**: `PhoneCall` entity `StateCode` and `StatusCode` options
 
 
-|`StateCode`|`StatusCode`|
+|StateCode|StatusCode|
 |---------|---------|
 |0 : Open|1: Open|
 |1 : Completed|2: Made <br />4: Received|
diff --git a/powerapps-docs/developer/common-data-service/multi-select-picklist.md b/powerapps-docs/developer/common-data-service/multi-select-picklist.md
@@ -89,7 +89,7 @@ The following examples shows the use of `ContainValues` and `not-contain-values`
 
 ### Contact entity values
 
-|`fullname`| `sample_outdooractivities` |
+|'fullname' attribute| 'sample_outdooractivities' attribute |
 |--------|-------------------|
 |Wayne Yarborough|1,9|
 |Monte Orton|2|
diff --git a/powerapps-docs/developer/common-data-service/org-service/metadata-retrieve-detect-changes.md b/powerapps-docs/developer/common-data-service/org-service/metadata-retrieve-detect-changes.md
@@ -83,7 +83,7 @@ The classes in the <xref:Microsoft.Xrm.Sdk.Metadata.Query> namespace and the <xr
   
  The following table lists <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata> properties that cannot be used in a <xref:Microsoft.Xrm.Sdk.Metadata.Query.MetadataFilterExpression>:  
   
-|||||  
+|Properties|Properties (cont'd)|Properties (cont'd)|Properties (cont'd)|  
 |-|-|-|-|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.Attributes>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.Description>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.DisplayCollectionName>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.DisplayName>|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.ManyToManyRelationships>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.ManyToOneRelationships>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.OneToManyRelationships>|<xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.Privileges>|  
@@ -249,7 +249,7 @@ EntityProperties.PropertyNames.AddRange(new string[] { "Attributes" });
   
  The following table lists <xref:Microsoft.Xrm.Sdk.Metadata.AttributeMetadata> properties that cannot be used in a <xref:Microsoft.Xrm.Sdk.Metadata.Query.MetadataFilterExpression>  
   
-|||  
+|Properties|Properties (cont'd)|  
 |-|-|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.AttributeMetadata.Description>|<xref:Microsoft.Xrm.Sdk.Metadata.AttributeMetadata.DisplayName>|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.EnumAttributeMetadata.OptionSet>|<xref:Microsoft.Xrm.Sdk.Metadata.LookupAttributeMetadata.Targets>|  
@@ -283,7 +283,7 @@ AttributeProperties.PropertyNames.Add("AttributeType");
   
  The following table lists Relationship metadata properties that cannot be used in a MetadataFilterExpression:  
   
-||  
+|Properties|  
 |-|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata>.<xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata.AssociatedMenuConfiguration>|  
 |<xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata>.<xref:Microsoft.Xrm.Sdk.Metadata.OneToManyRelationshipMetadata.CascadeConfiguration>|  
diff --git a/powerapps-docs/developer/common-data-service/org-service/use-filterexpression-class.md b/powerapps-docs/developer/common-data-service/org-service/use-filterexpression-class.md
@@ -21,9 +21,8 @@ In Common Data Service, you can use the <xref:Microsoft.Xrm.Sdk.Query.FilterExpr
   
  The following table lists the properties for the <xref:Microsoft.Xrm.Sdk.Query.FilterExpression> class.  
   
-|||  
-|-|-|  
-|Property|Description|  
+|Property|Description|
+|-|-|
 |<xref:Microsoft.Xrm.Sdk.Query.FilterExpression.Conditions>|Gets or sets condition expressions that include attributes, condition operators, and attribute values.|  
 |<xref:Microsoft.Xrm.Sdk.Query.FilterExpression.FilterOperator>|Gets or sets logical `AND/OR` filter operators. This is set by using the <xref:Microsoft.Xrm.Sdk.Query.LogicalOperator> enumeration.|  
 |<xref:Microsoft.Xrm.Sdk.Query.FilterExpression.Filters>|Gets or sets a hierarchy of condition and logical filter expressions that filter the results of the query.|  
diff --git a/powerapps-docs/developer/common-data-service/org-service/use-messages.md b/powerapps-docs/developer/common-data-service/org-service/use-messages.md
@@ -84,7 +84,7 @@ More information:
 
 You can pass optional parameters in messages using the <xref:Microsoft.Xrm.Sdk.OrganizationRequest.Parameters> property that is exposed for all the *Request message classes in the SDK assemblies. There are two optional parameters you can pass with messages
 
-|`Parameter`|Description|Messages|  
+|Parameter|Description|Messages|  
 |-----------------|-----------------|--------------|  
 |`SolutionUniqueName`|A `String` that specifies the unique name of the solution to which the operation applies. More information: [Dependency tracking for solution components](../dependency-tracking-solution-components.md).|<xref:Microsoft.Crm.Sdk.Messages.AddPrivilegesRoleRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.DeleteRequest> <br /> <xref:Microsoft.Crm.Sdk.Messages.MakeAvailableToOrganizationTemplateRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.UpdateRequest>|  
 |`SuppressDuplicateDetection`|A `Boolean` used to disable duplicate detection on a create or update operation. More information: [Use SuppressDuplicateDetection parameter to throw errors when you create or update record](detect-duplicate-data.md#use-suppressduplicatedetection-parameter-to-throw-errors-when-you-create-or-update-record) .|<xref:Microsoft.Xrm.Sdk.Messages.CreateRequest> <br /> <xref:Microsoft.Xrm.Sdk.Messages.UpdateRequest>|  
diff --git a/powerapps-docs/developer/common-data-service/store-appsource-package-azure-storage.md b/powerapps-docs/developer/common-data-service/store-appsource-package-azure-storage.md
@@ -35,40 +35,39 @@ To upload your package to Azure Blob storage:
 2. Sign in to Azure Management portal at [https://portal.azure.com](https://portal.azure.com).
 3. Create a new Storage account by clicking  > **Storage** > **Storage account - blob, file, table, queue**.
     
-   ![](media/appsource-storageaccount-pic1.png)
+   Create a Storage account](media/appsource-storageaccount-pic1.png)
 
 4. On the **Create storage account** page, specify **Name**, **Resource group**, and **Location** for your storage account. Leave the rest of the fields with the default options. Click **Create**. 
 
-   ![](media/appsource-storageaccount-pic2.png)
- 
+   ![Specifying account values](media/appsource-storageaccount-pic2.png)
   
 5. After your storage account is created, navigate to the newly created resource group, and create a new Blob container. Under **Blob Service**, select **Containers**, and then **+ Container**.
 
-   ![](media/appsource-storageaccount-pic3.png)
+   ![Create a new Blob container](media/appsource-storageaccount-pic3.png)
 
 6. Specify a name for your container, and select the **Public access level** as **Blob**. Click **OK**.
 
-   ![](media/appsource-storageaccount-pic4.png)
+   ![Set access level of the Blob](media/appsource-storageaccount-pic4.png)
 
 7. Start Azure Storage Explorer on your computer, and connect to your Azure Storage account by signing in using the same account with which you created your Azure Storage account.
 
 8. In Azure Storage Explorer, select the newly created container, and then select **Upload** > **Upload Files** to upload the app source package that you created in [Step 4: Create an AppSource package for your app](create-package-app-appsource.md). 
 
-   ![](media/appsource-storageaccount-pic5.png)
+   ![Upload the app source package](media/appsource-storageaccount-pic5.png)
 
 9. Browse to the AppSource package file on your computer, and select to upload it.
 
 10. Right-click on the uploaded AppSource package file, and select **Get Shared Access Signature**.
 
-    ![](media/appsource-storageaccount-pic6.png)
+    ![Selecting Shared Access Signature](media/appsource-storageaccount-pic6.png)
 
 11. On the **Shared Access Signature** page, modify the **Expiry time** value to make the Shared Access Signature (SAS) active for a month from the **Start time**. Click **Create**.
 
-    ![](media/appsource-storageaccount-pic7.png)
+    ![Set an expiration time](media/appsource-storageaccount-pic7.png)
 
 12. The next page displays information about the generated SAS information. Copy the **URL** value and save it for later. You will need to specify this URL while creating an offer in the Cloud Partner Portal.
 
-    ![](media/appsource-storageaccount-pic8.png)
+    ![Copying the SAS URL](media/appsource-storageaccount-pic8.png)
 
 
 > [!div class="nextstepaction"]
diff --git a/powerapps-docs/developer/common-data-service/use-webhooks.md b/powerapps-docs/developer/common-data-service/use-webhooks.md
@@ -339,7 +339,7 @@ Webhooks are relatively simple. The service will send the request and evaluate t
 
 The timeout is 60 seconds. Generally, if no response is returned before the timeout period or if the response `StatusCode` value is not within the `2xx` range to indicate success it will fail. The exception is when the error returned is in the following table:
 
-|`StatusCode`|Description|
+|StatusCode|Description|
 |-|-|
 |`502`|Bad Gateway|
 |`503`|Service Unavailable|
diff --git a/powerapps-docs/developer/common-data-service/webapi/use-postman-perform-operations.md b/powerapps-docs/developer/common-data-service/webapi/use-postman-perform-operations.md
@@ -143,9 +143,9 @@ More information: [Update and delete entities using the Web API](update-delete-e
 
 ## Use a function
 
-Use a `GET` request with the functions listed in [Web API Function Reference](https://docs.microsoft.com/dynamics365/customer-engagement/web-api/functions?view=dynamics-ce-odata-9) to perform reusable operations with the Web API. The example that follows shows how to send a Web API request that uses the <xref href="Microsoft.Dynamics.CRM.RetrieveDuplicates?text=RetrieveDuplicates function" /> to detect and retrieve duplicates of a specified record.
+Use a `GET` request with the functions listed in [Web API Function Reference](https://docs.microsoft.com/dynamics365/customer-engagement/web-api/functions?view=dynamics-ce-odata-9) to perform reusable operations with the Web API. The example that follows shows how to send a Web API request that uses the <xref:Microsoft.Dynamics.CRM.RetrieveDuplicates?text=RetrieveDuplicates function /> to detect and retrieve duplicates of a specified record.
 
-|||
+|HTTP method|URL|
 |----|----|
 |`GET`|`{{webapiurl}}RetrieveDuplicates(BusinessEntity=@p1,MatchingEntityName=@p2,PagingInfo=@p3)?@p1={'@odata.type':'Microsoft.Dynamics.CRM.account','accountid':'`*&lt;accountid&gt;*`'}&@p2='account'&@p3={'PageNumber':1,'Count':50}`|
 
diff --git a/powerapps-docs/developer/common-data-service/webapi/use-web-api-functions.md b/powerapps-docs/developer/common-data-service/webapi/use-web-api-functions.md
@@ -55,13 +55,13 @@ Parameter aliases also allow you to re-use parameter values to reduce the total
 
 ## Pass reference to an entity to a function
 
-Certain functions will require passing a reference to an existing entity. For example, the following functions have a parameter that requires a <xref href="Microsoft.Dynamics.CRM.crmbaseentity?text=crmbaseentity EntityType" />:  
+Certain functions will require passing a reference to an existing entity. For example, the following functions have a parameter that requires a <xref:Microsoft.Dynamics.CRM.crmbaseentity?text=crmbaseentity EntityType/>:  
   
-||||  
+|Functions|Functions (cont'd)|Functions (cont'd)|  
 |-|-|-|  
-|<xref href="Microsoft.Dynamics.CRM.CalculateRollupField?text=CalculateRollupField Function" />|<xref href="Microsoft.Dynamics.CRM.IncrementKnowledgeArticleViewCount?text=IncrementKnowledgeArticleViewCount Function" />|<xref href="Microsoft.Dynamics.CRM.InitializeFrom?text=InitializeFrom Function" />|  
-|<xref href="Microsoft.Dynamics.CRM.IsValidStateTransition?text=IsValidStateTransition Function" />|<xref href="Microsoft.Dynamics.CRM.RetrieveDuplicates?text=RetrieveDuplicates Function" />|<xref href="Microsoft.Dynamics.CRM.RetrieveLocLabels?text=RetrieveLocLabels Function" />|  
-|<xref href="Microsoft.Dynamics.CRM.RetrievePrincipalAccess?text=RetrievePrincipalAccess Function" />|<xref href="Microsoft.Dynamics.CRM.RetrieveRecordWall?text=RetrieveRecordWall Function" />|<xref href="Microsoft.Dynamics.CRM.ValidateRecurrenceRule?text=ValidateRecurrenceRule Function" />|  
+|<xref:Microsoft.Dynamics.CRM.CalculateRollupField?text=CalculateRollupField Function/>|<xref:Microsoft.Dynamics.CRM.IncrementKnowledgeArticleViewCount?text=IncrementKnowledgeArticleViewCount Function/>|<xref:Microsoft.Dynamics.CRM.InitializeFrom?text=InitializeFrom Function/>|  
+|<xref:Microsoft.Dynamics.CRM.IsValidStateTransition?text=IsValidStateTransition Function/>|<xref:Microsoft.Dynamics.CRM.RetrieveDuplicates?text=RetrieveDuplicates Function/>|<xref:Microsoft.Dynamics.CRM.RetrieveLocLabels?text=RetrieveLocLabels Function/>|  
+|<xref:Microsoft.Dynamics.CRM.RetrievePrincipalAccess?text=RetrievePrincipalAccess Function/>|<xref:Microsoft.Dynamics.CRM.RetrieveRecordWall?text=RetrieveRecordWall Function/>|<xref:Microsoft.Dynamics.CRM.ValidateRecurrenceRule?text=ValidateRecurrenceRule Function/>|  
   
 When you pass a reference to an existing entity, use the `@odata.id` annotation to the Uri for the entity. For example if you are using the <xref href="Microsoft.Dynamics.CRM.RetrievePrincipalAccess?text=RetrievePrincipalAccess Function" /> you can use the following Uri to specify retrieving access to a specific contact:  
   
@@ -179,12 +179,12 @@ There are two ways that functions can be used to control data returned with quer
 
 Some functions listed in <xref:Microsoft.Dynamics.CRM.FunctionIndex> will return a collection of entities. A subset of these functions are *composable*, which means that you can include an additional `$select` or `$filter` system query option to control which columns are returned in the results. These functions have an `IsComposable` attribute in the CSDL. Each of these functions has a companion message in the organization service that accept either a <xref:Microsoft.Xrm.Sdk.Query.ColumnSet> or <xref:Microsoft.Xrm.Sdk.Query.QueryBase> type parameter. The OData system query options provide the same functionality so these functions do not have the same parameters as their companion messages in the organization service. The following table shows a list of those composable functions in this release.  
   
-||||  
+|Functions|Functions (cont'd)|Functions (cont'd)|  
 |-|-|-|  
-|<xref href="Microsoft.Dynamics.CRM.GetDefaultPriceLevel?text=GetDefaultPriceLevel Function" />|<xref href="Microsoft.Dynamics.CRM.RetrieveAllChildUsersSystemUser?text=RetrieveAllChildUsersSystemUser Function" />|<xref href="Microsoft.Dynamics.CRM.RetrieveBusinessHierarchyBusinessUnit?text=RetrieveBusinessHierarchyBusinessUnit Function" />|  
-|<xref href="Microsoft.Dynamics.CRM.RetrieveByGroupResource?text=RetrieveByGroupResource Function" />|<xref href="Microsoft.Dynamics.CRM.RetrieveByResourceResourceGroup?text=RetrieveByResourceResourceGroup Function" />|<xref href="Microsoft.Dynamics.CRM.RetrieveMembersBulkOperation?text=RetrieveMembersBulkOperation Function" />|  
-|<xref href="Microsoft.Dynamics.CRM.RetrieveParentGroupsResourceGroup?text=RetrieveParentGroupsResourceGroup Function" />|<xref href="Microsoft.Dynamics.CRM.RetrieveSubGroupsResourceGroup?text=RetrieveSubGroupsResourceGroup Function" />|<xref href="Microsoft.Dynamics.CRM.RetrieveUnpublishedMultiple?text=RetrieveUnpublishedMultiple Function" />|  
-|<xref href="Microsoft.Dynamics.CRM.SearchByBodyKbArticle?text=SearchByBodyKbArticle Function" />|<xref href="Microsoft.Dynamics.CRM.SearchByKeywordsKbArticle?text=SearchByKeywordsKbArticle Function" />|<xref href="Microsoft.Dynamics.CRM.SearchByTitleKbArticle?text=SearchByTitleKbArticle Function" />|  
+|<xref:Microsoft.Dynamics.CRM.GetDefaultPriceLevel?text=GetDefaultPriceLevel Function />|<xref:Microsoft.Dynamics.CRM.RetrieveAllChildUsersSystemUser?text=RetrieveAllChildUsersSystemUser Function />|<xref:Microsoft.Dynamics.CRM.RetrieveBusinessHierarchyBusinessUnit?text=RetrieveBusinessHierarchyBusinessUnit Function />|  
+|<xref:Microsoft.Dynamics.CRM.RetrieveByGroupResource?text=RetrieveByGroupResource Function />|<xref:Microsoft.Dynamics.CRM.RetrieveByResourceResourceGroup?text=RetrieveByResourceResourceGroup Function />|<xref:Microsoft.Dynamics.CRM.RetrieveMembersBulkOperation?text=RetrieveMembersBulkOperation Function />|  
+|<xref:Microsoft.Dynamics.CRM.RetrieveParentGroupsResourceGroup?text=RetrieveParentGroupsResourceGroup Function />|<xref:Microsoft.Dynamics.CRM.RetrieveSubGroupsResourceGroup?text=RetrieveSubGroupsResourceGroup Function />|<xref:Microsoft.Dynamics.CRM.RetrieveUnpublishedMultiple?text=RetrieveUnpublishedMultiple Function />|  
+|<xref:Microsoft.Dynamics.CRM.SearchByBodyKbArticle?text=SearchByBodyKbArticle Function />|<xref:Microsoft.Dynamics.CRM.SearchByKeywordsKbArticle?text=SearchByKeywordsKbArticle Function />|<xref:Microsoft.Dynamics.CRM.SearchByTitleKbArticle?text=SearchByTitleKbArticle Function />|  
   
 <a name="bkmk_queryevaluationFunctions"></a>
   
diff --git a/powerapps-docs/developer/common-data-service/webapi/web-api-query-data-sample.md b/powerapps-docs/developer/common-data-service/webapi/web-api-query-data-sample.md
@@ -45,9 +45,9 @@ This sample is divided into the following principal sections, containing Web API
 |[Parameter alias](#bkmk_parameteralias)|[Use parameter aliases with system query options](query-data-web-api.md#bkmk_useParameterAliases)|
 |[Limit results](#bkmk_limitresults)|[Limit results](query-data-web-api.md#bkmk_limitResults)<br /><br /> [Limits on number of entities returned](query-data-web-api.md#bkmk_limits)|
 |[Expanding results](#bkmk_expandresults)|[Retrieve related entities by expanding navigation properties](query-data-web-api.md#bkmk_expandRelated)|
+|[Predefined queries](#bkmk_predefinedqueries)|[Retrieve and execute predefined queries](retrieve-and-execute-predefined-queries.md)<br /><br /> <xref:Microsoft.Dynamics.CRM.userquery?text=userquery EntityType/><br /><br /> <xref:Microsoft.Dynamics.CRM.savedquery?text=savedquery EntityType/>|
 <!-- TODO:
 |[FetchXML queries](#bkmk_fetchxml)|[FetchXML schema](../org-service/fetchxml-schema.md)<br /><br /> [Page large result sets with FetchXML](../org-service/page-large-result-sets-with-fetchxml.md)<br /><br /> [Use custom FetchXML](retrieve-and-execute-predefined-queries.md#bkmk_useFetchXML)| -->
-|[Predefined queries](#bkmk_predefinedqueries)|[Retrieve and execute predefined queries](retrieve-and-execute-predefined-queries.md)<br /><br /> <xref href="Microsoft.Dynamics.CRM.userquery?text=userquery EntityType" /><br /><br /> <xref href="Microsoft.Dynamics.CRM.savedquery?text=savedquery EntityType" />|
 
 The following sections contain a brief discussion of the Common Data Service Web API operations performed, along with the corresponding HTTP messages and associated console output.
 
diff --git a/powerapps-docs/developer/common-data-service/webapi/web-api-versions.md b/powerapps-docs/developer/common-data-service/webapi/web-api-versions.md
@@ -46,7 +46,7 @@ For v9.*x* instances, nothing gets appended to the attribute name.
 
 The following operations have been added to the Web API for the v9.x release.  
   
-||||  
+|Operations|Operations (cont'd)|Operations (cont'd)|  
 |-|-|-|  
 |<xref:Microsoft.Crm.Sdk.Messages.GrantAccessRequest>|<xref:Microsoft.Crm.Sdk.Messages.ModifyAccessRequest>|<xref:Microsoft.Crm.Sdk.Messages.RetrieveSharedPrincipalsAndAccessRequest>|  
 
diff --git a/powerapps-docs/developer/common-data-service/workflow/workflow-extensions.md b/powerapps-docs/developer/common-data-service/workflow/workflow-extensions.md
@@ -49,14 +49,14 @@ By default, these processes include a common set of activities you can perform a
 
 You can use the **Perform Action** activity to execute any custom actions or the following system messages called **Command Actions**:
 
-||||
+|Actions|Actions (cont'd)|Actions (cont'd)|
 |--|--|--|
 |AddToQueue|AddUserToRecordTeam|RemoveUserFromRecordTeam|
 |SetProcess|SetWordTemplate||
 
 If you have Dynamics 365 Sales or Service solutions, you can find other command actions depending on the solution:
 
-||||
+|Actions|Actions (cont'd)|Actions (cont'd)|
 |--|--|--|
 |ApplyRoutingRule|CalculateActualValue|CloseOpportunity|
 |GetQuoteProductsFromOpportunity|GetSalesOrderProductsFromOpportunity|LockInvoicePricing|
@@ -132,7 +132,7 @@ When your custom workflow activity uses input or output parameters you must add
 
 You can use the following types of properties as input or output parameters:
 
-||||
+|Properties|Properties (cont'd)|Properties (cont'd)|
 |--|--|--|
 |[bool](/dotnet/api/system.boolean)|[DateTime](/dotnet/api/system.datetime)|[Decimal](/dotnet/api/system.decimal)|
 |[Double](/dotnet/api/system.double)|<xref:Microsoft.Xrm.Sdk.EntityReference>|[int](/dotnet/api/system.int32)|
diff --git a/powerapps-docs/developer/component-framework/reference/client/getclient.md b/powerapps-docs/developer/component-framework/reference/client/getclient.md
@@ -35,7 +35,7 @@ Type: `String`
 
 Returns a value to indicate in which client the script is executing.
 
-|||
+|Client type|Description|
 |-----|-----|
 |Web| Web application, or Unified Interface|
 |Outlook| Outlook|
diff --git a/powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-data-process/stage/getNavigationBehavior.md b/powerapps-docs/developer/model-driven-apps/clientapi/reference/formContext-data-process/stage/getNavigationBehavior.md
@@ -39,7 +39,7 @@ stageObj.getNavigationBehavior().allowCreateNew = function () {
 
 For example, here is the **Create** button in the **Develop** stage of the **AccountToContactProcess** sample business process flow that lets you create a Contact record from the Account form.
 
-![](../../../../media/clientapi_getNavigationBehavior.png)
+![Create button in the Develop stage](../../../../media/clientapi_getNavigationBehavior.png)
 
 The `allowCreateNew` property will return **undefined** for business process flow records that do not implement cross-entity navigation.
 
diff --git a/powerapps-docs/developer/model-driven-apps/sample-import-files-web-resources.md b/powerapps-docs/developer/model-driven-apps/sample-import-files-web-resources.md
