Generated.

[homepage.git] / blog / index.html

diff --git a/blog/index.html b/blog/index.html
index 6d449f60ff5d24aa51408e628ffc72c43b1d1082..6ef5883eb7f589e0a3ce5a7408753de7c4dccf9e 100644 (file)
--- a/blog/index.html
+++ b/blog/index.html
@@ -26,8 +26,8 @@
 solution for use at home.  My requirements are simple, it must be
 cheap and locally encrypted (in other words, I keep the encryption
 keys, the storage provider do not have access to my private files).
-One idea me and my friends have had many years ago, before the cloud
-storage providers showed up, have been to use Google mail as storage,
+One idea me and my friends had many years ago, before the cloud
+storage providers showed up, was to use Google mail as storage,
 writing a Linux block device storing blocks as emails in the mail
 service provided by Google, and thus get heaps of free space.  On top
 of this one can add encryption, RAID and volume management to have
@@ -56,7 +56,7 @@ package is included already.  So to get started, run <tt>apt-get
 install s3ql</tt>.  Next, pick a storage provider.  I ended up picking
 Greenqloud, after reading their nice recipe on
 <a href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy">how
-to use s3ql with their Amazon S3 service</a>, because I trust the laws
+to use S3QL with their Amazon S3 service</a>, because I trust the laws
 in Iceland more than those in USA when it come to keeping my personal
 data safe and private, and thus would rather spend money on a company
 in Iceland.  Another nice recipe is available from the article
@@ -226,7 +226,7 @@ Backend reports that fs is still mounted elsewhere, aborting.
 <p>The file content is uploaded when the cache is full, while the
 metadata is uploaded once every 24 hour by default.  To ensure the
 file system content is flushed to the cloud, one can either umount the
-file system, or ask s3ql to flush the cache and metadata using
+file system, or ask S3QL to flush the cache and metadata using
 s3qlctrl:
 
 <p><blockquote><pre>
@@ -281,7 +281,7 @@ check out the mounted S3QL file system to see if it would be usable as
 a home directory (in other word, that it provided POSIX semantics when
 it come to locking and umask handling etc).  Running
 <a href="http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html">my
-test code to check file system semantics, I was happy to discover that
+test code to check file system semantics</a>, I was happy to discover that
 no error was found.  So the file system can be used for home
 directories, if one chooses to do so.</p>