Skip to content

Commit

Permalink
Website: Remove non-existent anchor to failures. Reword on homepage t…
Browse files Browse the repository at this point in the history
…o make is less misleading.
  • Loading branch information
Golmote committed Mar 26, 2018
1 parent 259b6fc commit 8c0911a
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion faq.html
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ <h1>Isn’t it bad to do syntax highlighting with regular expressions?</h1>
<p>For this reason, most syntax highlighters on the web and on desktop, are powered by regular expressions. This includes the internal syntax
highlighters used by popular native applications like Espresso and Sublime Text, at the time of writing.
Of course, not every regex-powered syntax highlighter is created equal. The number and type of failures can be vastly different, depending on
the exact algorithm used. <a href="examples.html#failures">Prism’s known failures are documented in the Examples section</a>.</p>
the exact algorithm used. <a href="examples.html">Prism’s known failures are documented in the Examples section</a>.</p>
</section>

<section>
Expand Down
2 changes: 1 addition & 1 deletion index.html
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ <h1>Full list of features</h1>
<h1>Limitations</h1>
<ul>
<li>Any pre-existing HTML in the code will be stripped off. <a href="faq.html#if-pre-existing-html-is-stripped-off-how-can-i-highlight">There are ways around it though</a>.</li>
<li>Regex-based so it *will* fail on <a href="examples.html#failures">certain edge cases</a>.</li>
<li>Regex-based so it *will* fail on certain edge cases, which are documented in the <a href="examples.html">Examples section</a>.</li>
<li>No IE 6-8 support. If someone can read code, they are probably in the 85% of the population with a modern browser.</li>
</ul>
</section>
Expand Down

0 comments on commit 8c0911a

Please sign in to comment.