peer review feedback incorporated

Author: SnehaSudhirG

articles/automation/automation-runbook-execution.md

@@ -122,7 +122,7 @@ Your runbooks can use self-signed certificates, which are not signed by a certif
 
 ## Jobs
 
-Azure Automation supports an environment to run jobs from the same Automation account. A single runbook can have many jobs running at one time. The more jobs you run at the same time, the more often they can be dispatched to the same sandbox. A maximum of 10 jobs can run in a sandbox. Sandbox would be removed when no jobs are executing in it, hence it should not be used to save files.
+Azure Automation supports an environment to run jobs from the same Automation account. A single runbook can have many jobs running at one time. The more jobs you run at the same time, the more often they can be dispatched to the same sandbox. A maximum of 10 jobs can run in a sandbox. A sandbox will be removed when no jobs are executing in it; hence, it shouldn't be used to save files.
 
 Jobs running in the same sandbox process can affect each other. One example is running the [Disconnect-AzAccount](/powershell/module/az.accounts/disconnect-azaccount) cmdlet. Execution of this cmdlet disconnects each runbook job in the shared sandbox process. For an example of working with this scenario, see [Prevent concurrent jobs](manage-runbooks.md#prevent-concurrent-jobs).
 

articles/automation/automation-runbook-types.md

@@ -87,7 +87,7 @@ The following are the current limitations and known issues with PowerShell runbo
 - PowerShell 7.x currently does not support signed runbooks.
 - Source control integration doesn't support PowerShell 7.1 (preview) Also, PowerShell 7.1 (preview) runbooks in source control gets created in Automation account as Runtime 5.1.
 - PowerShell 7.1 module management is not supported through `Get-AzAutomationModule` cmdlets.
-- Runbook will fail with no log trace, if input value contains character ’.
+- Runbook will fail with no log trace if the input value contains the character '.
 
 
 **Known issues**
@@ -125,7 +125,7 @@ The following are the current limitations and known issues with PowerShell runbo
 - Currently, PowerShell 7.2 (preview) runbooks are only supported from Azure portal. Rest API and PowerShell is not supported.
 - Az module 8.3.0 is installed by default and cannot be managed at the automation account level. Use custom modules to override the Az module to the desired version.
 - The imported PowerShell 7.2 (preview) module would be validated during job execution. Ensure that all dependencies for the selected module are also imported for successful job execution.
-- PowerShell 7.2 module management is not supported through `Get-AzAutomationModule`  cmdlets  
+- PowerShell 7.2 module management is not supported through `Get-AzAutomationModule`  cmdlets. 
 
 **Known issues**
 

articles/automation/runbook-input-parameters.md

@@ -112,7 +112,7 @@ For an example of how to use input parameters in a Python runbook, see
 [My first Python runbook in Azure Automation](./learn/automation-tutorial-runbook-textual-python-3.md).
 
 >[!NOTE]
->Arguments with spaces are currently not supported. As a workaround, you could use \\t in addition to \\n.
+>Arguments with spaces are currently not supported. As a workaround, you could use \\\t in addition to \\\n.
 
 ## Assign values to input parameters in runbooks