| commit | ccfbbb5d6ffa8b5195295a41aa249da72aa97fb6 | [log] [tgz] |
|---|---|---|
| author | Alex Gough <[email protected]> | Tue May 16 14:42:19 2023 |
| committer | Chromium LUCI CQ <[email protected]> | Tue May 16 14:42:19 2023 |
| tree | e0fa4df05f809f6fac34dae343d684db4488b844 | |
| parent | 3e327103d7ed79011ba39c9b754401f8200f1772 [diff] [blame] |
Fix toc/heading Missed a </a> which broke display. Bug: None Change-Id: I14d48db84775c30afa06125972d48e5d6df6371d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4535104 Commit-Queue: Robert Sesek <[email protected]> Reviewed-by: Robert Sesek <[email protected]> Auto-Submit: Alex Gough <[email protected]> Cr-Commit-Position: refs/heads/main@{#1144722}
diff --git a/docs/security/faq.md b/docs/security/faq.md index ce8f9c7..b7bf570 100644 --- a/docs/security/faq.md +++ b/docs/security/faq.md
@@ -47,7 +47,7 @@ there is no need to further assess the risk of Chromium vulnerabilities: we strive to fix vulnerabilities quickly and release often. -<a name="TOC-How-can-I-know-which-fixes-to-include-in-my-downstream-project-"> +<a name="TOC-How-can-I-know-which-fixes-to-include-in-my-downstream-project-"></a> ### How can I know which fixes to include in my downstream project? Chrome is built with mitigations and hardening which aim to prevent or reduce