Minor fixes

Author: jasminemehndir

articles/automation/automation-runbook-types.md

@@ -26,7 +26,7 @@ The Azure Automation Process Automation feature supports several types of runboo
 To learn about the process automation environment, see [Runbook execution in Azure Automation](automation-runbook-execution.md).
 
 > [!NOTE]
-> Azure Automation will follow the support lifecycle of PowerShell and Python language versions in accordance with the timelines published by parent the products, [PowerShell](/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.3&preserve-view=true#powershell-end-of-support-dates) and [Python](https://devguide.python.org/versions/), respectively. We recommend that you to use runbooks with supported language versions.
+> Azure Automation will follow the support lifecycle of PowerShell and Python language versions in accordance with the timelines published by parent the products, [PowerShell](/powershell/scripting/install/powershell-support-lifecycle?view=powershell-7.3&preserve-view=true#powershell-end-of-support-dates) and [Python](https://devguide.python.org/versions/), respectively. We recommend that you use runbooks with supported language versions.
 
 Take into account the following considerations when determining which type to use for a particular runbook:
 
@@ -328,7 +328,7 @@ Currently, Python 3.10 runtime version is supported for both Cloud and Hybrid jo
 ### Advantages
 
 > [!NOTE]
-> Importing a Python package may take several minutes. The advantages are:
+> Importing a Python package may take several minutes.
 
 - Uses the robust Python libraries.
 - Can run in Azure or on Hybrid Runbook Workers.
@@ -339,7 +339,7 @@ Currently, Python 3.10 runtime version is supported for both Cloud and Hybrid jo
 
 ### Limitations
 
-Following are the limitations of Python runbooks
+The limitations of Python runbooks are:
 
 # [Python 3.10](#tab/py10)
 

articles/automation/manage-runtime-environment.md

@@ -21,7 +21,7 @@ This article provides information on how to create Runtime Environment and perfo
 
 Before you assign permissions to managed identities, ensure you meet these prerequisites:
 
-An Azure Automation account is supported in all public regions except Brazil Southeast and Gov clouds.
+- An Azure Automation account is supported in all public regions except Brazil Southeast and Gov clouds.
 
 
 ## Switch between Runtime environment and old experience
@@ -42,7 +42,7 @@ To switch to Runtime environment, follow these steps:
 
 ### Old experience
 
-To switch to the old experience, follow these steps:
+To switch to the old experience, follow this step:
 
 1. Go to your Automation account, under **Process Automation**, the **Runtime environments** is removed and under **Shared resources**, **Modules** and **Python packages** can be seen.
 
@@ -56,13 +56,14 @@ To switch to the old experience, follow these steps:
 
 ### Create Runtime environment
 
-To create a Runtime environment in Azure portal, follow these steps:
-
 #### [Azure portal](#tab/create-runtime-portal)
+
+To create a Runtime environment, follow these steps:
+
 1. Sign in to the [Azure portal](https://portal.azure.com) and select your Automation account.
 1. In the **Overview** page, select **Try Runtime Environment experience**, if not already in the new experience.
 1. Under **Process Automation**, select **Runtime Environments** and then select **Create**.
-1. On **Basics**, enter the following details:
+1. On the **Basics** tab, enter the following details:
     1. **Name** for the Runtime environment. It must begin with alphabet and can contain only alphabets, numbers, underscores, and dashes.  
     1. From the **Language** drop-down, select the scripting language for Runtime environment.
         - Choose **PowerShell** for PowerShell scripting language or **Python** for Python scripting language.
@@ -137,10 +138,10 @@ https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<reso
 
 ### List Runtime environments
 
-To list all the Runtime environments from the Automation account, follow these steps:
-
 #### [Azure portal](#tab/list-runtime-portal)
 
+To list all the Runtime environments from the Automation account, follow these steps:
+
 1. In your Automation account, under **Process Automation**, select **Runtime Environments**.
 
    :::image type="content" source="./media/manage-runtime-environment/list-runtime-environment.png" alt-text="Screenshot shows how to view the list of all runtime environments." lightbox="./media/manage-runtime-environment/list-runtime-environment.png":::
@@ -164,10 +165,10 @@ Job output would show all the component packages and their versions.
 
 ### Delete Runtime environment
 
-To delete the Runtime environment from the Automation account, follow these steps:
-
 #### [Azure portal](#tab/delete-runtime-portal)
 
+To delete the Runtime environment from the Automation account, follow these steps:
+
 1. In your Automation account, under **Process Automation**, select **Runtime Environments**.
 1. Select the runtime environment that you want to delete.
 1. Select **Delete** to delete the Runtime environment.
@@ -186,10 +187,10 @@ https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<reso
 
 Runtime language and Runtime version are immutable properties. However, you can update the version of modules and add or remove packages in the Runtime environment. Runbooks linked to the Runtime environment are automatically updated with the new settings.
 
-To update a Runtime environment, follow these steps:
-
 #### [Azure portal](#tab/update-runtime-portal)
 
+To update a Runtime environment, follow these steps:
+
 1. In your Automation account, under **Process Automation**, select **Runtime Environments**.
 1. Select the Runtime environment that you want to update.
 1. Select the version from dropdown to update the version of existing packages.