summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorArtyom V. Poptsov <poptsov.artyom@gmail.com>2017-01-04 00:51:19 +0300
committerArtyom V. Poptsov <poptsov.artyom@gmail.com>2017-01-04 00:51:19 +0300
commitab6d420b53c91e5d8647356e02708fa72e0c3aa4 (patch)
tree89f508bd2f5502c3a549ff2e0e2bd4a3edd63558 /doc
parentguile-ssh.texi (Introduction): Update (diff)
downloadguile-ssh-ab6d420b53c91e5d8647356e02708fa72e0c3aa4.tar.gz
doc/guile-ssh.texi (Introduction): Fix some typos
Diffstat (limited to 'doc')
-rw-r--r--doc/guile-ssh.texi12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/guile-ssh.texi b/doc/guile-ssh.texi
index 8e55691..ea92359 100644
--- a/doc/guile-ssh.texi
+++ b/doc/guile-ssh.texi
@@ -98,12 +98,12 @@ struggling to achieve.
For me, the main goal is to provide convenient means to write truly
distributed applications in my favourite programming language.
-Computers getting cheaper and more and more ubiquitous, and so different kind
-of networks. In my opinion the question is -- how we are going to utilize
-those new computational resources? Using multi-core systems effectively may
-be tricky; fortunately some languages (such as as Scheme/GNU Guile) already
-provide convenient API to utilize those systems. But what about systems that
-distributed over a network?
+Computers are getting cheaper and more and more ubiquitous, and so different
+kind of networks. In my opinion the question is -- how we are going to
+utilize those new computational resources? Using multi-core systems
+effectively may be tricky; fortunately some languages (such as Scheme/GNU
+Guile) already provide convenient API to utilize those systems. But what
+about systems that distributed over a network?
I am dreaming of the times when using computer resources distributed over a
network in GNU Guile will be as easy as using local ones. You should not be