From fdda11168c0d822f74e217a82ca623191bd73100 Mon Sep 17 00:00:00 2001
From: Rizky <41568558+James868@users.noreply.github.com>
Date: Tue, 12 Mar 2019 02:57:49 +0000
Subject: [PATCH] Fix some typo
---
2-ui/5-data-storage/01-cookie/article.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/2-ui/5-data-storage/01-cookie/article.md b/2-ui/5-data-storage/01-cookie/article.md
index ae14d0c2..a3b33f81 100644
--- a/2-ui/5-data-storage/01-cookie/article.md
+++ b/2-ui/5-data-storage/01-cookie/article.md
@@ -166,7 +166,7 @@ document.cookie = "user=John; max-age=0";
The cookie should be transferred only over HTTPS.
-**By default if we set a cookie at `http://site.com`, then it also appears at `https://site.com` and vise versa.**
+**By default, if we set a cookie at `http://site.com`, then it also appears at `https://site.com` and vise versa.**
That is, cookies only check the domain, they do not distinguish between the protocols.
@@ -262,7 +262,7 @@ But if a cookie is `httpOnly`, then `document.cookie` doesn't see it, so it is p
## Appendix: Cookie functions
-Here's a small set of functions to work with cookies, more conveinent than a manual modification of `document.cookie`.
+Here's a small set of functions to work with cookies, more convenient than a manual modification of `document.cookie`.
There exist many cookie libraries for that, so these are for demo purposes. Fully working though:
@@ -348,7 +348,7 @@ Together: [cookie.js](cookie.js).
A cookie is called "third-party" if it's placed by domain other than the user is visiting.
For instance:
-1. A page at `site.com` loads an banner from another site: `
`.
+1. A page at `site.com` loads a banner from another site: ``.
2. Along with the banner, the remote server at `ads.com` may set `Set-Cookie` header with cookie like `id=1234`. Such cookie originates from `ads.com` domain, and will only be visible at `ads.com`:
@@ -357,7 +357,7 @@ For instance:
-4. What's even more important, when the users moves from `site.com` to another site `other.com` that also has a banners, then `ads.com` gets the cookie, as it belongs to `ads.com`, thus recognizing the visitor and tracking him as he moves between sites:
+4. What's even more important, when the users moves from `site.com` to another site `other.com` that also has a banner, then `ads.com` gets the cookie, as it belongs to `ads.com`, thus recognizing the visitor and tracking him as he moves between sites:
