From 24ac3420eab46cc31cf6a8b53919423e8d1244b7 Mon Sep 17 00:00:00 2001
From: aln363 <146224490+aln363@users.noreply.github.com>
Date: Mon, 18 Dec 2023 17:58:12 -0500
Subject: [PATCH] added text

---
 index.html | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 06dbcba..91c3c38 100644
--- a/index.html
+++ b/index.html
@@ -125,8 +125,11 @@ If the error message includes other parts of the command, such as a flag, that i
           <p><b>Killed:</b></p>
           <p>"killed" does not appear as a normal error message, but will show up at the end of the progress of the command, and the point at which it appears can vary. Sometimes, after you run a command it will be "killed" immediately, only making it through one frame before terminating, as in this example:</p>
         <p><img src="img/first_frame_killed.png" alt="command killed at first frame example" img></p>
-        <p><b>Error splitting argument list: option not found:</b></p>
         <p><b>Could not find tag for codec:</b></p> 
+        <h5>Filters</h5>
+          <p>When using filters, there are a handful of errors that may pop up. While this section certainly does not cover them all, below you will find a couple of possible errors and what could be causing them.</p>
+             <p><b>Error splitting argument list: option not found:</b></p>
+        <h2>Streams</h2>
       <!-- End Troubleshooting Common Issues --> 
     </div>
     <div class="well">