summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorJonathan Lebon <jonathan@jlebon.com>2018-05-07 09:41:27 -0400
committerAtomic Bot <atomic-devel@projectatomic.io>2018-05-08 14:49:59 +0000
commit053efeb23a16c63028e25d42eb942d8f84ef5534 (patch)
tree4f07ab0c6d8d221ae98af6028e2685549251f68a /README.md
parenta3295ee584a107784c34fea8616140b1e6ecdf94 (diff)
downloadostree-053efeb23a16c63028e25d42eb942d8f84ef5534.tar.gz
docs: Add "Hello World" example
Let's get practical faster in the manual and have a simple "Hello World" example right off the bat to hopefully make it easier to grok how OSTree works. Also some minor tweaks on wording around comparisons to git. Closes: #1581 Approved by: cgwalters
Diffstat (limited to 'README.md')
-rw-r--r--README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index c54151d1..36bcfc24 100644
--- a/README.md
+++ b/README.md
@@ -20,9 +20,9 @@ bootloader configuration.
The core OSTree model is like git in that it checksums individual files and has
a content-addressed-object store. It's unlike git in that it "checks out" the
-files via hardlinks, and they should thus be immutable. Therefore, another way
-to think of OSTree is that it's just a more polished version
-of
+files via hardlinks, and they thus need to be immutable to prevent corruption.
+Therefore, another way to think of OSTree is that it's just a more polished
+version of
[Linux VServer hardlinks](http://linux-vserver.org/index.php?title=util-vserver:Vhashify&oldid=2285).
**Features:**