Fixing grammar and spacing for better readability

Author: dbaduck

docs/relational-databases/logs/change-the-target-recovery-time-of-a-database-sql-server.md

@@ -28,7 +28,7 @@ manager: craigg
 ###  <a name="Restrictions"></a> Limitations and Restrictions 
 
 > [!CAUTION]  
->  An online transactional workload on a database that is configured for indirect checkpoints could experience performance degradation. Indirect checkpoints make sure that the number of dirty pages are below a certain threshold so that the database recovery completes within the target recovery time. The recovery interval configuration option uses the number of transactions to determine the recovery time as opposed to indirect checkpoints which makes use of number of dirty pages. When indirect checkpoints are enabled on a database receiving a large number of DML operations, the background writer can start aggressively flushing dirty buffers to disk to ensure that the time required to perform recovery is within the target recovery time set of the database. This can cause additional I/O activity on certain systems which can contribute to a performance bottleneck if the disk subsystem is operating above or nearing the I/O threshold.  
+>  An online transactional workload on a database that is configured for indirect checkpoints could experience performance degradation. Indirect checkpoints make sure that the number of dirty pages are below a certain threshold so that the database recovery completes within the target recovery time. The recovery interval configuration option uses the number of transactions to determine the recovery time as opposed to indirect checkpoints which makes use of the number of dirty pages. When indirect checkpoints are enabled on a database receiving a large number of DML operations, the background writer can start aggressively flushing dirty buffers to disk to ensure that the time required to perform recovery is within the target recovery time set on the database. This can cause additional I/O activity on certain systems, which can contribute to a performance bottleneck if the disk subsystem is operating above or nearing the I/O threshold.  
   
 ###  <a name="Security"></a> Security  
 
@@ -40,20 +40,20 @@ manager: craigg
 
 1.  In **Object Explorer**, connect to an instance of the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)], and expand that instance.  
 
-2.  Right-click the database you want to change, and click the **Properties** command.  
+2.  Expand the **Databases** container, then right-click the database you want to change, and click the **Properties** command.  
 
 3.  In the **Database Properties** dialog box, click the **Options** page.  
 
-4.  In the **Recovery** panel, in the **Target Recovery Time (Seconds)** field, specify the number of seconds that you want as the upper-bound on the recovery time for this database.  
+4.  In the **Recovery** panel, in the **Target Recovery Time (Seconds)** field, specify the number of seconds that you want as the upper-bound of the recovery time for this database.  
 
 ##  <a name="TsqlProcedure"></a> Using Transact-SQL  
  **To change the target recovery time**  
 
 1.  Connect to the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] where the database resides.  
 
-2.  Use the following [ALTER DATABASE](../../t-sql/statements/alter-database-transact-sql-set-options.md)statement, as follows:  
+2.  Use the following [ALTER DATABASE](../../t-sql/statements/alter-database-transact-sql-set-options.md) statement, as follows:  
 
-     TARGET_RECOVERY_TIME **=**_target_recovery_time_ { SECONDS | MINUTES }  
+     TARGET_RECOVERY_TIME **=** _target_recovery_time_ { SECONDS | MINUTES }  
 
      *target_recovery_time*  
      Beginning with [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)], the default value is 1 minute. When greater than 0 (the default for older versions), specifies the upper-bound on the recovery time for the specified database in the event of a crash.