summaryrefslogtreecommitdiffstats
path: root/doc/legacy/user-guide.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/legacy/user-guide.texi')
-rw-r--r--doc/legacy/user-guide.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/legacy/user-guide.texi b/doc/legacy/user-guide.texi
index 8e42985..31ff9cf 100644
--- a/doc/legacy/user-guide.texi
+++ b/doc/legacy/user-guide.texi
@@ -260,7 +260,7 @@ The specific changes made to @acronym{FUSE} are:
@itemize
@item The communication channel size between @acronym{FUSE} kernel module and GlusterFS has been increased to 1MB, permitting large reads and writes to be sent in bigger chunks.
-@item The kernel's read-ahead boundry has been extended upto 1MB.
+@item The kernel's read-ahead boundary has been extended up to 1MB.
@item Block size returned in the @command{stat()}/@command{fstat()} calls tuned to 1MB, to make cp and similar commands perform I/O using that block size.
@@ -554,7 +554,7 @@ can ensure this by running:
@end example
Before we can run the GlusterFS client or server programs, we need to write
-two files called @emph{volume specifications} (equivalently refered to as @emph{volfiles}).
+two files called @emph{volume specifications} (equivalently referred to as @emph{volfiles}).
The volfile describes the @emph{translator tree} on a node. The next chapter will
explain the concepts of `translator' and `volume specification' in detail. For now,
just assume that the volfile is like an NFS @command{/etc/export} file.
@@ -1198,7 +1198,7 @@ and in which order to evaluate them. This is done through the
Each sub-scheduler needs to know two things: when to kick in (the
entry-threshold), and how long to stay in control (the
exit-threshold). For example: when unifying three disks of 100GB,
-keeping an exact balance of disk-usage is not necesary. Instead, there
+keeping an exact balance of disk-usage is not necessary. Instead, there
could be a 1GB margin, which can be used to nicely balance other
factors, such as read-usage. The disk-usage scheduler can be told to
kick in only when a certain threshold of discrepancy is passed, such
@@ -1597,7 +1597,7 @@ This mode of write-behind operation is best used on the client side, to
enable decreased write latency for the application.
The write-behind translator can also aggregate write requests. If the
-@command{aggregate-size} option is specified, then successive writes upto that
+@command{aggregate-size} option is specified, then successive writes up to that
size are accumulated and written in a single operation. This mode of operation
is best used on the server side, as this will decrease the disk's head movement
when multiple files are being written to in parallel.
@@ -1655,7 +1655,7 @@ useful in a web hosting environment, where most clients will simply
read some files and only a few will write to them).
The IO cache translator reads data from its child in @command{page-size} chunks.
-It caches data upto @command{cache-size} bytes. The cache is maintained as
+It caches data up to @command{cache-size} bytes. The cache is maintained as
a prioritized least-recently-used (@acronym{LRU}) list, with priorities determined
by user-specified patterns to match filenames.