Merge pull request MicrosoftDocs#319 from nschonni/fix--MD038/no-space-in-code

fix: MD038/no-space-in-code

Author: KumarVivek

powerapps-docs/developer/common-data-service/org-service/generate-early-bound-classes.md

@@ -37,7 +37,7 @@ The classes created by the code generation tool are designed to be built into a
 The following lists assemblies that must be referenced in your project when you use the generated code file.  
 
 - `Microsoft.Crm.Sdk.Proxy.dll`  
-- `Microsoft.Xrm.Sdk.dll ` 
+- `Microsoft.Xrm.Sdk.dll` 
 
 These assemblies are part of the [Microsoft.CrmSdk.CoreAssemblies](https://www.nuget.org/packages/Microsoft.CrmSdk.CoreAssemblies/) NuGet package. Use this Nuget packages to add these assemblies to your Visual Studio project.
 

powerapps-docs/developer/common-data-service/tutorial-write-plug-in.md

@@ -209,7 +209,7 @@ In Visual Studio, press **F6** to build the assembly. Verify that it compiles wi
 1. Click **OK** to close the **Create Strong Name Key** dialog.
 1. In the project properties **Build** tab, verify that the **Configuration** is set to **Debug**.
 1. Press **F6** to build the plug-in again.
-1. Using windows explorer, find the built plug-in at:` \bin\Debug\BasicPlugin.dll`.
+1. Using windows explorer, find the built plug-in at: `\bin\Debug\BasicPlugin.dll`.
 
 > [!NOTE]
 > Build the assembly using **Debug** configuration because you will use the Plug-in profiler to debug it in a later tutorial.   Before you include a plug-in with your solution, you should build it using the release configuration.

powerapps-docs/developer/common-data-service/use-change-tracking-synchronize-data-external-systems.md

@@ -22,7 +22,7 @@ The change tracking feature in Common Data Service provides a way to keep the da
 <a name="BKMK_enable"></a>   
 ## Enable change tracking for an entity  
 
- Before retrieving the changes for an entity, make sure that the change tracking feature is enabled for that entity. This feature can be enabled by using the customization user interface (UI) or programmatically by setting the <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.ChangeTrackingEnabled> property to `True`. Annotation `Org.OData.Capabilities.V1.ChangeTracking ` gets added to entity sets that have change tracking enabled. To see annotations in entity metadata, do 
+ Before retrieving the changes for an entity, make sure that the change tracking feature is enabled for that entity. This feature can be enabled by using the customization user interface (UI) or programmatically by setting the <xref:Microsoft.Xrm.Sdk.Metadata.EntityMetadata.ChangeTrackingEnabled> property to `True`. Annotation `Org.OData.Capabilities.V1.ChangeTracking` gets added to entity sets that have change tracking enabled. To see annotations in entity metadata, do 
 
  ```http 
  GET [Organization URI]/api/data/v9.0/$metadata?annotations=true

powerapps-docs/developer/model-driven-apps/create-manage-model-driven-apps-using-code.md

@@ -225,8 +225,9 @@ Accept: application/json
 
 To disassociate a security role from a Model-driven app, you use the DELETE request with the same navigation property. For example:
 
-`DELETE	[Organization URI]/api/data/v9.0/appmodules(dd621d4a-d898-e711-80e7-00155db763be)/appmoduleroles_association/$ref?$id=[Organization URI]/api/data/v9.0/roles(<roleId)
-`
+```
+DELETE	[Organization URI]/api/data/v9.0/appmodules(dd621d4a-d898-e711-80e7-00155db763be)/appmoduleroles_association/$ref?$id=[Organization URI]/api/data/v9.0/roles(<roleId)
+```
 
 ## Manage your model-driven apps and its components
 

powerapps-docs/maker/canvas-apps/controls/control-power-bi-tile.md

@@ -38,11 +38,15 @@ By passing a single parameter from the app, you can filter the results that appe
 
 To pass a single filter value, modify the value of the **TileURL** property, which follows this syntax:
 
-```"https://app.powerbi.com/embed?dashboardId=<DashboardID>&tileId=<TileID>&config=<SomeHash>" ```
+```
+"https://app.powerbi.com/embed?dashboardId=<DashboardID>&tileId=<TileID>&config=<SomeHash>"
+```
 
 To that value, append this syntax:
 
-```&$filter=<TableName>/<ColumnName> eq '<Value>' ```
+```
+&$filter=<TableName>/<ColumnName> eq '<Value>'
+```
 
 The parameter will filter a value in the dataset of the report where the tile originates.
 

powerapps-docs/maker/common-data-service/virtual-entity-odata-provider-requirements.md

@@ -52,9 +52,9 @@ The following table lists the OData Entity Data Model (EDM) data type mappings w
 
 ### OData EDM data types that are not supported for mapping with virtual entities 
 
-- `Edm.Binary `
+- `Edm.Binary`
 - `Edm.Time` 
-- `Edm.Float `
+- `Edm.Float`
 - `Edm.Single` 
 - `Edm.Int16` 
 - `Edm.Byte` 

powerapps-docs/maker/model-driven-apps/create-edit-web-resources.md

@@ -39,7 +39,7 @@ Web resources are virtual files stored in the system. Each web resource has a un
 
 For example, if you create an HTML page as a web resource named “new_myWebResource.htm”, you could open that page in a browser using a URL like this:  
 
-`<base URL>/WebResources/new_myWebResource.htm   `
+`<base URL>/WebResources/new_myWebResource.htm`
 
 where *\<base URL>* is the part of the URL you use to view apps that ends in `dynamics.com`. Because the web resource is data in the system, only licensed users for your organization can access them this way. Normally, web resources are included in forms rather than referenced directly. The most common usage is to provide JavaScript libraries for form scripts.