From 34be6e923cf8b5ce77d9d053ebc8eacd4c72d263 Mon Sep 17 00:00:00 2001
From: nickfreeman <nickfreemandesign@gmail.com>
Date: Tue, 18 Dec 2018 10:23:30 -0500
Subject: [PATCH] minor language fixes to readme

---
 4-frames-and-windows/03-cross-window-communication/article.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/4-frames-and-windows/03-cross-window-communication/article.md b/4-frames-and-windows/03-cross-window-communication/article.md
index a4193a62..d4f5504d 100644
--- a/4-frames-and-windows/03-cross-window-communication/article.md
+++ b/4-frames-and-windows/03-cross-window-communication/article.md
@@ -26,7 +26,7 @@ The "Same Origin" policy states that:
 - if we have a reference to another window, e.g. a popup created by `window.open` or a window inside `<iframe>`, and that window comes from the same origin, then we have full access to that window.
 - otherwise, if it comes from another origin, then we can't access the content of that window: variables, document, anything. The only exception is `location`: we can change it (thus redirecting the user). But we can't not *read* location (so we can't see where the user is now, no information leak).
 
-Now let's see how some examples. First, about pages that come from the same origin, and thus there are no limitations. And afterwards we'll cover cross-window messaging that allows to work around the "Same Origin" policy.
+Now let's see some examples. First, we'll look at pages that come from the same origin and do not conflict with the "Same Origin" policy, and afterwards we'll cover cross-window messaging that allows to work around the "Same Origin" policy.
 
 
 ````warn header="Subdomains may be same-origin"