| commit | 59877ec0b79b68b208b74387b9defdcc73931a20 | [log] [tgz] |
|---|---|---|
| author | Chris Palmer <[email protected]> | Fri Nov 22 01:28:09 2019 |
| committer | Commit Bot <[email protected]> | Fri Nov 22 01:28:09 2019 |
| tree | aafbd4d8c51f3e2729d9806d589112a7a08ee6b3 | |
| parent | e8eeaeb9131721cf39de7b96373da5b2b18f3087 [diff] [blame] |
Fix inverted words in Security FAQ document. Fix by 0xdade, proposed at https://github.com/chromium/chromium/pull/32/files. Thank you! Bug: None Change-Id: Id1ade1985c83aec49ad4bf6431ab25e3c20c2705 TBR: awhalley Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928241 Auto-Submit: Chris Palmer <[email protected]> Reviewed-by: Chris Palmer <[email protected]> Commit-Queue: Chris Palmer <[email protected]> Cr-Commit-Position: refs/heads/master@{#717959}
diff --git a/docs/security/faq.md b/docs/security/faq.md index d57a52e..5689f15 100644 --- a/docs/security/faq.md +++ b/docs/security/faq.md
@@ -417,7 +417,7 @@ useful security measure but it tightly couples client and server configurations and completely breaks when those configurations are out of sync. In order to manage that risk we need to ensure that we can promptly update pinning clients -an in emergency and ensure that non-emergency changes can be deployed in a +in an emergency and ensure that non-emergency changes can be deployed in a reasonable timeframe. Each of the conditions listed above helps ensure those properties: