english language fixes in README by my friend

1 files changed, 11 insertions, 14 deletions

diff --git a/docs/README b/docs/README
index bb3d4b7..5503ba7 100644
--- a/docs/README
+++ b/docs/README
@@ -1,32 +1,29 @@
 q. what is it ?
-a. this is my attempt to implement download manager for my needs with features i need which lost in most clients
+a. this is my attempt to implement download manager for my needs with features i need which are not available in most clients
 
 q. another download manager ? are you kidding ?
-a. no, not at all, i tried hard and not able to find software i want, most are very resource hungry, many does not have required minimum features set
+a. no, not at all, i tried hard and i was not able to find software i wanted, most are very resource hungry, many does not have required minimum features set
 
 q. ok, ok, so what the difference ?
 a. here are few key difference:
-1. client<->server model, so all work is done on server, also all data and metadata stored on server too (can be running locally if needed), and client are just gui (with all required for download manager abilities including download files/directories from server)
-2. mostly event based communication (this means i will try to avoid polling, loops and related mechanics as much as possible and instead fire events to both directions, also i will implement highly configurable events subscription mechanism)
-3. dynamic resource usage by this words i mean if you have high end server, you can configure udm to use as much resources as needed and do many many nice things, but if you have low end pc for server (and even routers like things) you can configure udm to work just fine on this type of hardware.
-and the same for client, due to event based architecture client should be able to subscript only for requred events also if this is refreshing data (like progress bar, download speed e.t.c.) firing timer should be configurable via subscription api
-4. all existing modern software are torrent clients and limited to torrent only (this is ok for today, but may not be for tomorrow), udm is modular by design so download protocols and all other features is just dynamicly loadable modules, we are not limited to single download protocol
+1. client<->server model, so all work is done on the server, also all data and metadata stored on server too (can run locally if needed), and client are just gui (with all required abilities for a download manager including downloading files/directories from server)
+2. mostly event based communication (this means i will try to avoid polling, loops and related mechanics as much as possible and instead fire events to both directions, also i will implement highly configurable event subscription mechanism)
+3. dynamic resource usage, by this words i mean if you have high end server, you can configure udm to use as much resources as needed and do many many nice things, but if you have low end pc for server (and even router like things) you can configure udm to work just fine on this type of hardware.
+and the same for client, due to event based architecture client should be able to subscribe only for requred events also if this is refreshing data (like progress bar, download speed e.t.c.) firing timer should be configurable via subscription api
+4. all existing modern software are torrent clients and limited to torrent only (this is ok for today, but may not be for tomorrow), udm is modular by design so download protocols and all other features is just dynamicly loadable modules, it's not limited to single download protocol
 
 q. ok, but we already have torrent clients wich have similar design and features, transmission, rtorrent + rutorrent and you still want to make another app with torrent support ?
-a. yes., i know, currently i using rtorrent + rutorrent for torrents, and screen + wget, curl for http/ftp/... , but i want single app, also all existing software do not fit my needs, for example transmission web and qbittorrent web missing some key features i really need,
-rtorrent + rutorrent are really nice, but it really resource hungry (on client side), it kill every browser if you have lots of downloads with lots of files.
+a. yes, i know, currently i use rtorrent + rutorrent for torrents, and screen + wget, curl for http/ftp/... , but i want single app, also all existing software doesn't fit my needs, for example transmission web and qbittorrent web are missing some key features i really need,
+rtorrent + rutorrent are really nice, but they are really resource hungry (on client side), they kill every browser if you have lot of downloads with lots of files.
 
 q. so, you said client<->server, do you mean just another web ui ?
 a. no, not really, server will work completely independent of client, all client<->server communications will done via special protocol (currently implemented with protobuf), so it's possible to implement any kind of client, i will implement crossplatform gui client in qt
 
-
 q. sounds interesting, am i be able to install udm on my low end router with external hdd ?
-a. oh, you are so fast, most probably yes, but not at time of first alpha release
-
+a. oh, you are so fast, most probably yes, but not at the time of first alpha release
 
 q. can i install server on windows ?
-a. most probably not out of the box, server targeted on unix machine, but i will not break compatibility with windows, it's just not planed by design, but it may work if you are lucky
-
+a. most probably not out of the box, server targeted on unix machine, but i will not break compatibility with windows, it's just not planned by design, but it may work if you are lucky
 
 q. i am interested, where can i download udm ?
 a. unfortunately currently you can't, for now you can monitor my git branch for changes or just wait. i have no date, no anything, it's not paid work, this just for fun. git repo: http://dark-alexandr.net/git/?p=misc.git;a=shortlog;h=refs/heads/unnamed_dm