Updated article

Author: MGoedtel

articles/automation/automation-managing-data.md

@@ -20,22 +20,22 @@ The following table summarizes the retention policy for different resources.
 
 | Data | Policy |
 |:--- |:--- |
-| Accounts |Permanently removed 90 days after the account is deleted by a user. |
-| Assets |Permanently removed 90 days after the asset is deleted by a user, or 90 days after the account that holds the asset is deleted by a user. |
-| Modules |Permanently removed 90 days after the module is deleted by a user, or 90 days after the account that holds the module is deleted by a user. |
-| Runbooks |Permanently removed 90 days after the resource is deleted by a user, or 90 days after the account that holds the resource is deleted by a user. |
-| Jobs |Deleted and permanently removed 90 days after last being modified. This could be after the job completes, is stopped, or is suspended. |
-| Node Configurations/MOF Files |Old node configuration is permanently removed 90 days after a new node configuration is generated. |
-| DSC Nodes |Permanently removed 90 days after the node is unregistered from Automation Account using Azure portal or the [Unregister-AzureRMAutomationDscNode](https://docs.microsoft.com/powershell/module/azurerm.automation/unregister-azurermautomationdscnode) cmdlet in Windows PowerShell. Nodes are also permanently removed 90 days after the account that holds the node is deleted by a user. |
+| Accounts |Permanently removed 30 days after the account is deleted by a user. |
+| Assets |Permanently removed 30 days after the asset is deleted by a user, or 30 days after the account that holds the asset is deleted by a user. |
+| Modules |Permanently removed 30 days after the module is deleted by a user, or 30 days after the account that holds the module is deleted by a user. |
+| Runbooks |Permanently removed 30 days after the resource is deleted by a user, or 30 days after the account that holds the resource is deleted by a user. |
+| Jobs |Deleted and permanently removed 30 days after last being modified. This could be after the job completes, is stopped, or is suspended. |
+| Node Configurations/MOF Files |Old node configuration is permanently removed 30 days after a new node configuration is generated. |
+| DSC Nodes |Permanently removed 30 days after the node is unregistered from Automation Account using Azure portal or the [Unregister-AzureRMAutomationDscNode](https://docs.microsoft.com/powershell/module/azurerm.automation/unregister-azurermautomationdscnode) cmdlet in Windows PowerShell. Nodes are also permanently removed 30 days after the account that holds the node is deleted by a user. |
 | Node Reports |Permanently removed 90 days after a new report is generated for that node |
 
 The retention policy applies to all users and currently cannot be customized.
 
-However, if you need to retain data for a longer period of time, you can forward runbook job logs to Azure Monitor logs.  For further information, review [forward Azure Automation job data to Azure Monitor logs](automation-manage-send-joblogs-log-analytics.md).   
+However, if you need to retain data for a longer period of time, you can forward runbook job logs to Azure Monitor logs. For further information, review [forward Azure Automation job data to Azure Monitor logs](automation-manage-send-joblogs-log-analytics.md).
 
 ## Backing up Azure Automation
 
-When you delete an automation account in Microsoft Azure, all objects in the account are deleted including runbooks, modules, configurations, settings, jobs, and assets. The objects cannot be recovered after the account is deleted.  You can use the following information to backup the contents of your automation account before deleting it. 
+When you delete an automation account in Microsoft Azure, all objects in the account are deleted including runbooks, modules, configurations, settings, jobs, and assets. The objects cannot be recovered after the account is deleted.  You can use the following information to backup the contents of your automation account before deleting it.
 
 ### Runbooks