From dbabfa649f6a70e3c0d30af958b9a371996e1aaa Mon Sep 17 00:00:00 2001
From: aln363 <146224490+aln363@users.noreply.github.com>
Date: Mon, 18 Dec 2023 16:53:35 -0500
Subject: [PATCH] ok actually fixed the hyperlink issue

---
 index.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index 1664849..06dbcba 100644
--- a/index.html
+++ b/index.html
@@ -111,10 +111,10 @@
        <input type="checkbox" id="troubleshooting">
       <div class="hiding"> 
           <h5>Troubleshooting Common Issues</h5>
-          <p>There are many common issues you may encounter when using FFmpeg. This section is here to provide some possible explanations and solutions.For more general solutions to issues regarding download, installation, and other possible questions or issues, please refer to the <a href="https://ffmpeg.org/faq.html">FFmpeg FAQ.</p>
-          <p>Before delving into some specific error messages and what may cause them, there are a few general tips you can follow to help make sure your files are doing what you want them to.
+          <p>There are many common issues you may encounter when using FFmpeg. This section is here to provide some possible explanations and solutions.For more general solutions to issues regarding download, installation, and other possible questions or issues, please refer to the <a href="https://ffmpeg.org/faq.html">FFmpeg FAQ.</a>
+<p>Before delving into some specific error messages and what may cause them, there are a few general tips you can follow to help make sure your files are doing what you want them to.
 First, always check that the output file actually opens, plays, looks, and/or sounds the way you intended it to. It is possible that FFmpeg will create an output file that, on the surface, looks correct, but upon further inspection, there may be inconsistencies with the codec, extension, or other file information, depending on what you intended to do with the file. 
-Second, always be certain that the file extension you are using for your output files is the intended extension. Within FFmpeg, certain extensions default to certain codecs, such as <code>.mp4</code> encoding to H.264. You always want to make sure that your extension coincides with your intended codec. A list of extensions and codec defaults can be found <a href="https://amiaopensource.github.io/ffmprovisr/#codec-defaults">here.</p>
+Second, always be certain that the file extension you are using for your output files is the intended extension. Within FFmpeg, certain extensions default to certain codecs, such as <code>.mp4</code> encoding to H.264. You always want to make sure that your extension coincides with your intended codec. A list of extensions and codec defaults can be found <a href="https://amiaopensource.github.io/ffmprovisr/#codec-defaults">here.</a></p>
 <h5>General Error Messages</h5>
           <p><b>Error: No such file or directory:</b> <img src="img/directory_error_example.png" alt="no such file or directory error message"img></p> 
           <p>There are a few reasons why this error may be appearing. First, check to make sure that you are in the correct directory. It can be easy to lose track of where your files are actually stored, especially on a personal computer. If you are working on a personal computer, the easiest way to do this is to check where your files                are. When working with MacOS, for example, files are often stored in the downloads or documents folders. To change your directory from home to this specific directory, use the command <code>cd</code> followed by your desired folder. For downloads, it would look like this:  <code>cd downloads</code></p>