Apply pencil edits for blocking issues from PR review

Author: Court72

docs/database-engine/configure-windows/scm-services-configure-sql-server-error-logs.md

@@ -22,7 +22,7 @@ This article describes how to view or modify the way [!INCLUDE [ssNoVersion](../
 
 1. In the **Configure SQL Server Error Logs** dialog box, choose from the following options.
 
-   1. Log files count
+   - Log files count
 
       **Limit the number of the error log files before they are recycled**
 
@@ -32,7 +32,7 @@ This article describes how to view or modify the way [!INCLUDE [ssNoVersion](../
 
       Specify the maximum number of archived error log files created before they're recycled. The default is 6, not including the current one. This value determines the number of previous backup logs that [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] retains before recycling them.
 
-   1. Log file size
+   - Log file size
 
       **Maximum size for error log file in KB**
 

docs/database-engine/configure-windows/scm-services-prevent-automatic-startup-of-an-instance.md

@@ -19,7 +19,7 @@ helpviewer_keywords:
 
 [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
 
-This article describes how prevent an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] from starting automatically in [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] by using SQL Server Configuration Manager. [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is normally configured to start automatically. You can change that by setting the start mode for the instance to manual.
+This article describes how to prevent an instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] from starting automatically in [!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] by using SQL Server Configuration Manager. [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] is normally configured to start automatically. You can change that by setting the start mode for the instance to manual.
 
 ## <a id="SSMSProcedure"></a> Use SQL Server Configuration Manager