Merge pull request #49422 from DCtheGeek/dmc-automation-patch2

Fixes MicrosoftDocs/azure-docs#13569 - Fix cmdlet and remove type

Author: PRMerger16

articles/automation/automation-dsc-compile.md

@@ -259,9 +259,9 @@ DSC configurations in Azure Automation can reference Automation credential asset
 `Get-AzureRmAutomationCredential`. If a configuration has a parameter that has a **PSCredential**
 type, then you can use the `Get-AutomationRmAutomationCredential` cmdlet by passing the string name
 of an Azure Automation credential asset to the cmdlet to retrieve the credential. You can then use
-then use that object for the parameter requiring the **PSCredential** object. Behind the scenes,
-the Azure Automation credential asset with that name is retrieved and passed to the configuration.
-The example below shows this in action.
+that object for the parameter requiring the **PSCredential** object. Behind the scenes, the Azure
+Automation credential asset with that name is retrieved and passed to the configuration. The
+example below shows this in action.
 
 Keeping credentials secure in node configurations (MOF configuration documents) requires encrypting
 the credentials in the node configuration MOF file. However, currently you must tell PowerShell DSC
@@ -280,7 +280,7 @@ The following example shows a DSC configuration that uses an Automation credenti
 Configuration CredentialSample
 {
     Import-DscResource -ModuleName PSDesiredStateConfiguration
-    $Cred = Get-AutomationRmAutomationCredential -ResourceGroupName 'ResourceGroup01' -AutomationAccountName 'ContosoAutomationAccount' -Name 'SomeCredentialAsset'
+    $Cred = Get-AutomationPSCredential 'SomeCredentialAsset'
 
     Node $AllNodes.NodeName
     {