diff --git a/5-network/05-fetch-crossorigin/1-do-we-need-origin/solution.md b/5-network/05-fetch-crossorigin/1-do-we-need-origin/solution.md
@@ -1,9 +1,9 @@
-We need `Origin`, because sometimes `Referer` is absent. For instance, when we `fetch` HTTP-page from HTTPS (access less secure from more secure), then there's no `Referer`.

-The [Content Security Policy](http://en.wikipedia.org/wiki/Content_Security_Policy) may forbid sending a `Referer`.

-As we'll see, `fetch` has options that prevent sending the `Referer` and even allow to change it (within the same site).

-By specification, `Referer` is an optional HTTP-header.

-Exactly because `Referer` is unreliable, `Origin` was invented. The browser guarantees correct `Origin` for cross-origin requests.
diff --git a/5-network/05-fetch-crossorigin/1-do-we-need-origin/task.md b/5-network/05-fetch-crossorigin/1-do-we-need-origin/task.md
@@ -2,11 +2,11 @@ importance: 5

---

-# Why do we need Origin?

-As you probably know, there's HTTP-header `Referer`, that usually contains an url of the page which initiated a network request.

-For instance, when fetching `http://google.com` from `http://javascript.info/some/url`, the headers look like this:

```
Accept: */*
@@ -20,9 +20,9 @@ Referer: http://javascript.info/some/url
*/!*
```

-As you can see, both `Referer` and `Origin` are present.

-The questions:

-1. Why `Origin` is needed, if `Referer` has even more information?
-2. Is it possible that there's no `Referer` or `Origin`, or is it incorrect?