Index: third_party/WebKit/Source/core/frame/csp/ContentSecurityPolicy.cpp |
diff --git a/third_party/WebKit/Source/core/frame/csp/ContentSecurityPolicy.cpp b/third_party/WebKit/Source/core/frame/csp/ContentSecurityPolicy.cpp |
index cb2a42ea2bf70b3d84f72c2792319eea1db45e52..bfd2989213fa2ab3c8e19c10ad32640ee1a4cf67 100644 |
--- a/third_party/WebKit/Source/core/frame/csp/ContentSecurityPolicy.cpp |
+++ b/third_party/WebKit/Source/core/frame/csp/ContentSecurityPolicy.cpp |
@@ -757,7 +757,7 @@ void ContentSecurityPolicy::reportViolation(const String& directiveText, const S |
// directive that was violated. The document's URL is safe to send because |
// it's the document itself that's requesting that it be sent. You could |
// make an argument that we shouldn't send HTTPS document URLs to HTTP |
- // report-uris (for the same reasons that we supress the Referer in that |
+ // report-uris (for the same reasons that we suppress the Referer in that |
// case), but the Referer is sent implicitly whereas this request is only |
// sent explicitly. As for which directive was violated, that's pretty |
// harmless information. |