Fix a few markdown errors in the security faq.
BUG=none
Change-Id: I50c20eac60163d3a552bbc69fb40a78629ddcf2d
Reviewed-on: https://chromium-review.googlesource.com/594567
Reviewed-by: Chris Palmer <[email protected]>
Commit-Queue: Avi Drissman <[email protected]>
Cr-Commit-Position: refs/heads/master@{#490796}diff --git a/docs/security/faq.md b/docs/security/faq.md
index 635d1c81..63898e71 100644
--- a/docs/security/faq.md
+++ b/docs/security/faq.md
@@ -192,8 +192,7 @@
extracting the password from any of these places.
<a name="TOC-Does-entering-JavaScript:-URLs-in-the-URL-bar-or-running-script-in-the-developer-tools-mean-there-s-an-XSS-vulnerability-"></a>
-## Does entering JavaScript: URLs in the URL bar or running script in the
-developer tools mean there's an XSS vulnerability?
+## Does entering JavaScript: URLs in the URL bar or running script in the developer tools mean there's an XSS vulnerability?
No. Chrome does not attempt to prevent the user from knowingly running script
against loaded documents, either by entering script in the Developer Tools
@@ -306,8 +305,7 @@
Chrome assumes that you have consented to HTTPS interception. Anyone who can add
a trust anchor to your computer can make other changes to your computer, too,
including changing Chrome. (See also [Why aren't physically-local attacks in
-Chrome's threat model?]
-](#TOC-Why-aren-t-physically-local-attacks-in-Chrome-s-threat-model-).)
+Chrome's threat model?](#TOC-Why-aren-t-physically-local-attacks-in-Chrome-s-threat-model-).)
<a name="TOC-Why-can-t-I-select-Proceed-Anyway-on-some-HTTPS-error-screens-"></a>
## Why can’t I select Proceed Anyway on some HTTPS error screens?
