Fixed failed HQRMtests

SharePointDsc/WikiSource/Contributing-to-SharePointDsc.md

@@ -12,14 +12,14 @@ The Get-TargetResource function should not return $null as a result. It may, how
 ```PowerShell
 function Get-TargetResource
 {
-	$nullreturn = @{
-            ServiceAppName = $ServiceAppName
-            Name = $Name
-            RequestLimit = $null
-            WaitTime = $null
-            Ensure = "Absent"
-	}
-	return $nullreturn
+    $nullreturn = @{
+      ServiceAppName = $ServiceAppName
+      Name           = $Name
+      RequestLimit   = $null
+      WaitTime       = $null
+      Ensure         = "Absent"
+    }
+    return $nullreturn
 }
 ```
 

SharePointDsc/WikiSource/Creating-Configuration-Files.md

@@ -10,16 +10,16 @@ a number of components that are common across all deployments.
 When describing a configuration for a SharePoint Server, there are a number of common
 components that are likely to exist in every configuration.
 Namely the components related to the installation of the product -
-[SPInstallPreReqs](SPInstallPreReqs) and [SPInstall](SPInstall).
+_[SPInstallPreReqs](SPInstallPreReqs)_ and _[SPInstall](SPInstall)_.
 
 It is also important to understand how the SharePointDsc resources impersonate and communicate
 with the SharePoint PowerShell cmdlet's.
 For PowerShell 5 (which we recommend) you should use the PsDscRunAsCredential property to specify
  the account a resource should run as.
 However for PowerShell 4 this is not an option, and the InstallAccount option is to be used in
 that situation, which relies on creating a local PowerShell session that uses CredSSP authentication.
-This means you are likely to want to use the xCredSSP resources also (see [Remote sessions and
-the InstallAccount variable](Remote-sessions-and-the-InstallAccount-variable)) for more information
+This means you are likely to want to use the xCredSSP resources also (see _[Remote sessions and
+the InstallAccount variable](Remote-sessions-and-the-InstallAccount-variable)_) for more information
 on this).
 There are also a limited number of scenario's in SharePointDsc that will always use this CredSSP
 approach (such as provisioning the user profile sync service) so it is recommended that even if
@@ -31,8 +31,8 @@ The single server deployment is the most straightforward - you will have one con
 that will describe all of the components that you want to have on that server.
 This is not likely to be a production deployment, but more a development or testing server.
 The specifics of what you put in to this configuration are largely up to what you want this server
-to be running, but you will always include [SPFarm](SPFarm) to create the farm, and
-[SPDistributedCacheService](SPDistributedCacheService) to enable the distributed cache service
+to be running, but you will always include _[SPFarm](SPFarm)_ to create the farm, and
+_[SPDistributedCacheService](SPDistributedCacheService)_ to enable the distributed cache service
 in the farm.
 The rest can be as little or as detailed as you need it to be in order to achieve your desired
 configuration.

SharePointDsc/WikiSource/Error-Exceeded-the-configured-MaxEnvelopeSize-quota.md

@@ -24,4 +24,4 @@ Change the network profile to Domain or Private in order to change the setting.
 ## More information
 More information about the MaxEnvelopeSize can be found at:
 * https://msdn.microsoft.com/en-us/library/cc251449.aspx
-* https://msdn.microsoft.com/en-us/library/aa384372%28VS.85%29.aspx
+* https://msdn.microsoft.com/en-us/library/aa384372%28VS.85%29.aspx

SharePointDsc/WikiSource/Export-SharePoint-Configuration.md

@@ -15,7 +15,7 @@ That is why Nik Charlebois created [ReverseDsc](https://www.powershellgallery.co
 This module offers generic functionalities to generate DSC configurations and requires a technology
 specific orchestrator script to export the data.
 
-> For a [Full list](Understanding-Resources) of what can be extracted have a look at our Included Resources section.
+> For a _[Full list](Understanding-Resources)_ of what can be extracted have a look at our Included Resources section.
 
 Since SharePointDsc v4.5, this orchestrator script (and therefore ReverseDsc support) has been
 natively integrated into SharePointDsc.

SharePointDsc/WikiSource/Getting-Started.md

@@ -18,4 +18,4 @@ This is useful in various scenarios, but can become complex depending how broad
 
 It's entirely possible that DSC is the right fit for you , and that there is a learning / discipline requirement. Or a Gap in your knowledge/ experience this Getting Started section is designed to help you.
 
-More information on PowerShell Desired State Configuration in general, can be found [here](https://docs.microsoft.com/en-us/powershell/scripting/dsc/overview/overview).
+More information on PowerShell Desired State Configuration in general, can be found [here](https://docs.microsoft.com/en-us/powershell/scripting/dsc/overview/overview).

SharePointDsc/WikiSource/Home.md

@@ -4,7 +4,7 @@ SharePointDsc v#.#.#
 
 Here you will find all the information you need to make use of the SharePoint DSC resources, including details of the resources that are available, current capabilities and known issues, and information to help plan a DSC based implementation of SharePoint.
 
-Please leave comments, feature requests, and bug reports in the [issues section](../issues) for this module.
+Please leave comments, feature requests, and bug reports in the [issues section](https://github.com/dsccommunity/SharePointDsc/issues) for this module.
 
 ## Quick start
 
@@ -17,7 +17,7 @@ To confirm installation, run the below command and ensure you see the SharePoint
 
     Get-DscResource -Module SharePointDsc
 
-To view a more detailed explanation, view our [Getting Started](Getting-Started) page.
+To view a more detailed explanation, view our _[Getting Started](Getting-Started)_ page.
 
 
 ## Supported SharePoint versions
@@ -36,11 +36,11 @@ SharePointDsc currently supports:
 ## Known Issues
 There are some known issues (and their solutions/workarounds) with SharePointDsc or PowerShell:
 
-[Error Exceeded the configured MaxEnvelopeSize quota](Error-Exceeded-the-configured-MaxEnvelopeSize-quota)
+_[Error Exceeded the configured MaxEnvelopeSize quota](Error-Exceeded-the-configured-MaxEnvelopeSize-quota)_
 
-[Setting up Central Administration on HTTPS](Setting-up-Central-Administration-on-HTTPS)
+_[Setting up Central Administration on HTTPS](Setting-up-Central-Administration-on-HTTPS)_
 
-[Using CredSSP on a domain controller / single server farm](Using-CredSSP-on-a-Domain-Controller)
+_[Using CredSSP on a domain controller / single server farm](Using-CredSSP-on-a-Domain-Controller)_
 
 ## Multilingual support
 
@@ -55,4 +55,4 @@ Resources inside the SharePointDSC module are categorized into 4 main groups.
 - Distributed Resources
 - Utility Resources
 
-To understand how to use these resources in your Configuration to avoid Syntax and undesired results go to our [Understanding Resources](Understanding-Resources) section.
+To understand how to use these resources in your Configuration to avoid Syntax and undesired results go to our _[Understanding Resources](Understanding-Resources)_ section.

SharePointDsc/WikiSource/Other-useful-modules-for-SharePoint-DSC-configurations.md

@@ -19,9 +19,9 @@ These resources can manage site configuring for tasks such as bindings, or remov
 
 Available at [https://www.powershellgallery.com/packages/xCredSSP](https://www.powershellgallery.com/packages/xCredSSP)
 
-The xCredSSP module is a simple way to automate CredSSP configuration. See [Remote sessions and the InstallAccount variable](Remote-sessions-and-the-InstallAccount-variable) for more information on this.
+The xCredSSP module is a simple way to automate CredSSP configuration. See _[Remote sessions and the InstallAccount variable](Remote-sessions-and-the-InstallAccount-variable)_ for more information on this.
 
-## SchannelDsc
+## SChannelDsc
 
 Available at [https://www.powershellgallery.com/packages/SchannelDsc](https://www.powershellgallery.com/packages/SchannelDsc)
 

SharePointDsc/WikiSource/Prerequisites.md

@@ -5,6 +5,6 @@ To use DSC on earlier versions of Windows, install the Windows Management Framew
 
 However it is strongly recommended that PowerShell 5.0 (or above) is used, as it adds support for the PsDscRunAsCredential parameter and has overall better performance and troubleshooting capabilities.
 
-The logic behind this is explained on the page "[Remote sessions and the InstallAccount variable](Remote-sessions-and-the-InstallAccount-variable)" page.
+The logic behind this is explained on the page _[Remote sessions and the InstallAccount variable](Remote-sessions-and-the-InstallAccount-variable)_ page.
 
 [PowerShell 5.1](https://www.microsoft.com/en-us/download/details.aspx?id=54616) includes significant improvements in Desired State Configuration and PowerShell Script Debugging.

SharePointDsc/WikiSource/Remote-sessions-and-the-InstallAccount-variable.md

@@ -36,7 +36,7 @@ This removes the need to have InstallAccount on SharePointDsc resources. However
 The SharePointDsc resources will detect if they are running as the local system account or not and will only use a "remote" session as described above where it is needed.
 
 Also note that some resources in SharePointDsc still use the above described remote session technique to simulate other others regardless of whether or not PsDscRunAsCredential is used.
-An example of this is [SPUserProfileSyncService](SPUserProfileSyncService) which uses this approach to run as the farm account value.
+An example of this is _[SPUserProfileSyncService](SPUserProfileSyncService)_ which uses this approach to run as the farm account value.
 
 An example of how to use this property in PowerShell 5 is shown below: