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 40fc72737fa8099116238163fbf380fe304b6294..71e71bc06525b37637630986bdb85dc8e0ff52e8 100644 |
--- a/third_party/WebKit/Source/core/frame/csp/ContentSecurityPolicy.cpp |
+++ b/third_party/WebKit/Source/core/frame/csp/ContentSecurityPolicy.cpp |
@@ -764,7 +764,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. |