diff options
author | Yun <melongbob@gmail.com> | 2018-07-04 08:29:18 -0700 |
---|---|---|
committer | Rigel Kent <par@rigelk.eu> | 2018-07-04 17:29:18 +0200 |
commit | c9e96ead93b2f6fb12d44ac3def136ae2bffc54b (patch) | |
tree | 00c2aabecd2089ddea843e73f5fda6826b6c2d29 | |
parent | 06aa2726d72cccbd7045b5c687b2357b096de4b9 (diff) | |
download | PeerTube-c9e96ead93b2f6fb12d44ac3def136ae2bffc54b.tar.gz PeerTube-c9e96ead93b2f6fb12d44ac3def136ae2bffc54b.tar.zst PeerTube-c9e96ead93b2f6fb12d44ac3def136ae2bffc54b.zip |
(doc) syntactic fixes (#764)
FAQ.md
- "the name" -> "a name"
- "re install" -> "reinstall"
- Changed the sentence structure to accomodate the flow of "objective -> method to achieve the objective -> reason why the objective is desired", rather than "how we are going to do it -> what we are trying to do -> why it is important"
README.md
- "It's the reason" -> "That is why"
- "in it" -> "on it"
- "This program is free software" -> "This is a free software": reduce redundancy (program and software), and introduce a proper article
- "redistribute it and/or modify it" -> "redistribute and/or modify it"
-rw-r--r-- | FAQ.md | 6 | ||||
-rw-r--r-- | README.md | 9 |
2 files changed, 7 insertions, 8 deletions
@@ -23,7 +23,7 @@ | |||
23 | ## I don't like the name "PeerTube" | 23 | ## I don't like the name "PeerTube" |
24 | 24 | ||
25 | PeerTube is just the name of the software. You can install it on your | 25 | PeerTube is just the name of the software. You can install it on your |
26 | server, and choose the name you want. For example, [this instance](https://framatube.org/) | 26 | server, and choose a name you want. For example, [this instance](https://framatube.org/) |
27 | is named "Framatube". | 27 | is named "Framatube". |
28 | 28 | ||
29 | ## If nobody watches a video, is it seeded? | 29 | ## If nobody watches a video, is it seeded? |
@@ -59,7 +59,7 @@ WEBM, MP4 or OGV videos. | |||
59 | 59 | ||
60 | ## I want to change my domain name, how can I do that? | 60 | ## I want to change my domain name, how can I do that? |
61 | 61 | ||
62 | You can't. You'll need to re install an instance and reupload your videos. | 62 | You can't. You'll need to reinstall an instance and reupload your videos. |
63 | 63 | ||
64 | 64 | ||
65 | ## Should I have a big server to run PeerTube? | 65 | ## Should I have a big server to run PeerTube? |
@@ -106,7 +106,7 @@ Moreover, don't forget that advertisers already pay considering YouTube's large | |||
106 | ## What is "creation dynamic" and why not modify it? | 106 | ## What is "creation dynamic" and why not modify it? |
107 | 107 | ||
108 | We define creation dynamic as the way any original content, regardless of its monetary value, is created and incentivized. | 108 | We define creation dynamic as the way any original content, regardless of its monetary value, is created and incentivized. |
109 | We want to limit as much as possible the influence our platform could have on authors in order to stay neutral. We are not curators, and want to limit the scope of PeerTube instance owners and administrators' responsibilities to moderation tasks only. | 109 | We want to stay neutral by limiting the influence of our platform on authors as much as possible. We are not curators, and want to limit the scope of PeerTube instance owners and administrators' responsibilities to moderation tasks only. |
110 | 110 | ||
111 | If you still want to use a functionality potentially altering that state of things, then you could interface with our upcoming plug-in system, which will be the place to integrate such features in the near future. | 111 | If you still want to use a functionality potentially altering that state of things, then you could interface with our upcoming plug-in system, which will be the place to integrate such features in the near future. |
112 | 112 | ||
@@ -90,8 +90,8 @@ enough money to pay for bandwidth and video storage of its servers. | |||
90 | 90 | ||
91 | So we need to have a decentralized network of servers seeding videos (as | 91 | So we need to have a decentralized network of servers seeding videos (as |
92 | [Diaspora](https://github.com/diaspora/diaspora) for example). But it's not | 92 | [Diaspora](https://github.com/diaspora/diaspora) for example). But it's not |
93 | enough because one video could become famous and overload the server. It's the | 93 | enough because one video could become famous and overload the server. That is |
94 | reason why we need to use a P2P protocol to limit the server load. Thanks to | 94 | why we need to use a P2P protocol to limit the server load. Thanks to |
95 | [WebTorrent](https://github.com/feross/webtorrent), we can make P2P (thus | 95 | [WebTorrent](https://github.com/feross/webtorrent), we can make P2P (thus |
96 | BitTorrent) inside the web browser, as of today. | 96 | BitTorrent) inside the web browser, as of today. |
97 | 97 | ||
@@ -156,7 +156,7 @@ See [ARCHITECTURE.md](/ARCHITECTURE.md) for a more detailed explanation. | |||
156 | torrent URI of this specific video is...). | 156 | torrent URI of this specific video is...). |
157 | * If a user uploads a video, the server seeds it and sends its followers some | 157 | * If a user uploads a video, the server seeds it and sends its followers some |
158 | metadata (name, short description, torrent URI...). | 158 | metadata (name, short description, torrent URI...). |
159 | * A server is a tracker responsible for all the videos uploaded in it. | 159 | * A server is a tracker responsible for all the videos uploaded on it. |
160 | * Even if nobody watches a video, it is seeded by the server (through | 160 | * Even if nobody watches a video, it is seeded by the server (through |
161 | [WebSeed protocol](http://www.bittorrent.org/beps/bep_0019.html)) where the | 161 | [WebSeed protocol](http://www.bittorrent.org/beps/bep_0019.html)) where the |
162 | video was uploaded. | 162 | video was uploaded. |
@@ -179,8 +179,7 @@ Copyright (C) 2018 PeerTube Contributors | |||
179 | 179 | ||
180 | This program is free software: you can redistribute it and/or modify | 180 | This program is free software: you can redistribute it and/or modify |
181 | it under the terms of the GNU Affero General Public License as published | 181 | it under the terms of the GNU Affero General Public License as published |
182 | by the Free Software Foundation, either version 3 of the License, or | 182 | by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. |
183 | (at your option) any later version. | ||
184 | 183 | ||
185 | This program is distributed in the hope that it will be useful, | 184 | This program is distributed in the hope that it will be useful, |
186 | but WITHOUT ANY WARRANTY; without even the implied warranty of | 185 | but WITHOUT ANY WARRANTY; without even the implied warranty of |