--- /home/clopez/webkit/webkit/layout-test-results/http/tests/security/mixedContent/insecure-audio-video-in-main-frame-expected.txt
+++ /home/clopez/webkit/webkit/layout-test-results/http/tests/security/mixedContent/insecure-audio-video-in-main-frame-actual.txt
@@ -1,5 +1,5 @@
-CONSOLE MESSAGE: The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-audio-video.html displayed insecure content from http://127.0.0.1:8080/resources/test.mp4.
+CONSOLE MESSAGE: The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-audio-video.html was allowed to display insecure content from http://127.0.0.1:8080/resources/test.mp4.
 
-CONSOLE MESSAGE: The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-audio-video.html displayed insecure content from http://127.0.0.1:8080/resources/test.mp4.
+CONSOLE MESSAGE: The page at https://127.0.0.1:8443/security/mixedContent/resources/frame-with-insecure-audio-video.html was allowed to display insecure content from http://127.0.0.1:8080/resources/test.mp4.
 
 This test opens a window that loads insecure HTML5 audio and video. We should trigger a mixed content callback because the main frame in the window is HTTPS but is displaying insecure content.