Commit fddef86e authored by Michał "rysiek" Woźniak's avatar Michał "rysiek" Woźniak 🔒

OVERVIEW.md: typo fix

parent 5cb4aa22
Pipeline #46312 passed with stage
in 6 minutes and 34 seconds
......@@ -135,7 +135,7 @@ Samizdat is divided into a few parts:
once loaded in a visitor's browser, it takes over handling all requests originating from the website, using plugins for content retrieval;
- **[plugins](./../plugins/)**
which implement different means of content retrieval, of which there are two kinds:
- *transport plugins*, handling retrieval of content from remote locations; this can be achieved by using a regular [HTTPS `fetch()`](./../plugins/fetch.js) to the original domain, or [via `IPFS`](./../plugins/gun-ipfs.js), or by requesting content from any other pre-configured location, or through any other means, as long as it's possible to implement it in JavaScript runningin the browser;
- *transport plugins*, handling retrieval of content from remote locations; this can be achieved by using a regular [HTTPS `fetch()`](./../plugins/fetch.js) to the original domain, or [via `IPFS`](./../plugins/gun-ipfs.js), or by requesting content from any other pre-configured location, or through any other means, as long as it's possible to implement it in JavaScript running in the browser;
- *stashing plugins*, which handle saving successfully retrieved content locally (for example using the [Cache API](https://developer.mozilla.org/en-US/docs/Web/API/Cache)) to be used in case the website is blocked.
You can read more about Samizdat's architecture [here](./ARCHITECTURE.md).
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment