Apply suggestions from code review

Jill Grant · web-flow · commit fe59825f1613 · 2024-06-12T20:26:23.000-06:00
Acrolinx fixes
diff --git a/docs/relational-databases/errors-events/mssqlserver-701-database-engine-error.md b/docs/relational-databases/errors-events/mssqlserver-701-database-engine-error.md
@@ -112,7 +112,7 @@ The following sections describe more detailed steps for each scenario - external
 - Review the System Event log and look for memory related errors (for example, low virtual memory).
 - Review the Application Event log for application-related memory issues.
 
-  Here is a sample PowerShell script to query the System and Applicaiton Event logs for the keyword "memory". Feel free to use other strings like "resource" for your search:
+  Here is a sample PowerShell script to query the System and Application Event logs for the keyword "memory". Feel free to use other strings like "resource" for your search:
 
   ```PowerShell
   Get-EventLog System -ComputerName "$env:COMPUTERNAME" -Message "*memory*"
diff --git a/docs/relational-databases/sql-server-transaction-log-architecture-and-management-guide.md b/docs/relational-databases/sql-server-transaction-log-architecture-and-management-guide.md
@@ -227,7 +227,7 @@ To restore a database up to the point of failure, the log chain must be intact.
 
 ### Restore log backups
 
-Restoring a log backup rolls forward the changes that were recorded in the transaction log to recreate the exact state of the database at the time the log backup operation started. When you restore a database, you'll have to restore the log backups that were created after the full database backup that you restore, or from the start of the first file backup that you restore. Typically, after you restore the most recent data or differential backup, you must restore a series of log backups until you reach your recovery point. Then, you recover the database. This rolls back all transactions that were incomplete when the recovery started and brings the database online. After the database has been recovered, you can't restore anymore backups. For more information, see [Apply Transaction Log Backups (SQL Server)](backup-restore/apply-transaction-log-backups-sql-server.md).
+Restoring a log backup rolls forward the changes that were recorded in the transaction log to recreate the exact state of the database at the time the log backup operation started. When you restore a database, you'll have to restore the log backups that were created after the full database backup that you restore, or from the start of the first file backup that you restore. Typically, after you restore the most recent data or differential backup, you must restore a series of log backups until you reach your recovery point. Then, you recover the database. This rolls back all transactions that were incomplete when the recovery started and brings the database online. After the database has been recovered, you can't restore any more backups. For more information, see [Apply Transaction Log Backups (SQL Server)](backup-restore/apply-transaction-log-backups-sql-server.md).
 
 ## Checkpoints and the active portion of the log
 
