summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/download_backends.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'community/gsoc/project_ideas/download_backends.mdwn')
-rw-r--r--community/gsoc/project_ideas/download_backends.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas/download_backends.mdwn b/community/gsoc/project_ideas/download_backends.mdwn
index aa4823de..a6e090eb 100644
--- a/community/gsoc/project_ideas/download_backends.mdwn
+++ b/community/gsoc/project_ideas/download_backends.mdwn
@@ -10,7 +10,7 @@ is included in the section entitled
[[meta title="Use Internet Protocol Translators (ftpfs etc.) as Backends for Other Programs"]]
-The Hurd design faciliates splitting up large applications into independent,
+The Hurd design facilitates splitting up large applications into independent,
generic components, which can be easily combined in different contexts, by
moving common functionality into separate Hurd servers (translators),
accessible trough filesystem interfaces and/or specialized RPC interfaces.
@@ -19,7 +19,7 @@ Download protocols like FTP, HTTP, BitTorrent etc. are very good candidates for
this kind of modularization: a program could simply use the download
functionality by accessing FTP, HTTP etc. translators.
-There is already an ftpfs traslator in the Hurd tree, as well as a [httpfs
+There is already an ftpfs traslator in the Hurd tree, as well as an [httpfs
translator on hurdextras](http://www.nongnu.org/hurdextras/#httpfs); however,
these are only suitable for very simple use cases: they just provide the actual
file contents downloaded from the URL, but no additional status information