TeamPiped-mirror/documentation
1
0
Fork 0
mirror of https://github.com/TeamPiped/documentation.git synced 2024-08-14 23:50:09 +00:00
Code Issues Projects Releases Packages Wiki Activity

fix typos

Browse source
This commit is contained in:
FireMasterK 2021-02-11 01:04:53 +05:30
parent 5c242335bf
commit caf756a6d1
No known key found for this signature in database
GPG key ID: 8DFF5DD33E93DB58
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/docs/architecture/index.md
View file

@ -23,7 +23,7 @@ links: https://github.com/TeamPiped/Piped\, https://github.com/TeamPiped/Piped-B
- Uses Java 11
- Uses the native HTTP client introduced in Java 9
- Uses netty-reactor to acheive maximum performance and a low footprint.
- Uses netty-reactor to achieve maximum performance and a low footprint.
- Supports OpenJ9
- Each running instance should configure their own proxy, thus allowing multi-gigabit content delivery.
- Uses ~70-130 MB of ram. (on OpenJ9)

4
content/docs/why/index.md
View file

@ -36,7 +36,7 @@ I created Piped to fix issues in NewPipe and Invidious which are architectural i
### NewPipe
- Your IP is exposed to YouTube.
- Feeds are slow to load/update in comparion to YouTube.
- Feeds are slow to load/update in comparison to YouTube.
### Invidious
@ -46,7 +46,7 @@ I created Piped to fix issues in NewPipe and Invidious which are architectural i
- Caching is done at a backend level.
- Invidious was a learning project.
- Invidious crashes all the time.
- Various hacks are required to keep an instance running at a reasonable stablity.
- Various hacks are required to keep an instance running at a reasonable stability.
However, there are some drawbacks of Piped: