Updating supportability items

Author: bobbytreed

articles/automation/automation-hrw-run-runbooks.md

@@ -16,8 +16,6 @@ There's no difference in the structure of runbooks that run in Azure Automation
 
 When you author runbooks to run on a Hybrid Runbook Worker, you should edit and test the runbooks within the machine that hosts the Hybrid worker. The host machine has all of the PowerShell modules and network access you need to manage and access the local resources. Once a runbook is tested on the Hybrid worker machine, you can then upload it to the Azure Automation environment where it's available to run in the Hybrid worker. It's important to know that jobs that run under the Local System account for Windows or a special user account `nxautomation` on Linux. On Linux, this means that you must ensure that the `nxautomation` account has access to the location where you store your modules. When you use the [Install-Module](/powershell/module/powershellget/install-module) cmdlet, specify **AllUsers** to the `-Scope` parameter to confirm that the `naxautomation` account has access.
 
-You can find a list of the sudo permissions used by the `nxautomation` account in the following [Sudoers file](https://github.com/microsoft/OMS-Agent-for-Linux/blob/master/installer/conf/sudoers).
-
 For more information on PowerShell on Linux, see [Known Issues for PowerShell on Non-Windows Platforms](https://docs.microsoft.com/powershell/scripting/whats-new/known-issues-ps6?view=powershell-6#known-issues-for-powershell-on-non-windows-platforms).
 
 ## Starting a runbook on Hybrid Runbook Worker