adding some clarifying text for a LOG_BACKUP and ACTIVE_TRANSACTION sections

Author: PiJoCoder

docs/relational-databases/logs/troubleshoot-a-full-transaction-log-sql-server-error-9002.md

@@ -251,6 +251,8 @@ DEALLOCATE no_truncate_db
   
 ### More information on LOG_BACKUP log_reuse_wait
 
+The most common actions you can consider here is to review your database recovery model and backup the transaction log of your database. 
+
 #### Recovery model
 
 Consider each database's to recovery model carefully. Perform log backups on all databases in FULL or BULK_LOGGED recovery models. For more information, see [Recovery Models](../backup-restore/recovery-models-sql-server.md)
@@ -299,6 +301,8 @@ ORDER BY bs.database_name asc, bs.Backup_Start_Date desc;
 
 ### More information on ACTIVE_TRANSACTION log_reuse_wait
 
+The steps to troubleshoot ACTIVE_TRANSACTION reason include discovering the long running transaction and resolving it (in some case using the KILL command to do so).
+
 #### Discover long-running transactions
 
 A very long-running transaction can cause the transaction log to fill. To look for long-running transactions, use one of the following: