summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2020-11-13 14:35:20 +0200
committerLars Wirzenius <liw@liw.fi>2020-11-13 14:35:20 +0200
commitf3fa2572c5c7258917e75a3a629f3b158b64f435 (patch)
tree3e9be57fe733321f61191321f1f600595df3003e
parent875464279c26bafbdb6234e3bb019107f52f0c73 (diff)
downloadobnam2-f3fa2572c5c7258917e75a3a629f3b158b64f435.tar.gz
doc: tighten and clean up the glossary
-rw-r--r--obnam.md15
1 files changed, 8 insertions, 7 deletions
diff --git a/obnam.md b/obnam.md
index 4a569b6..9c550a1 100644
--- a/obnam.md
+++ b/obnam.md
@@ -28,15 +28,16 @@ but not very simple copy-on-write B-tree structure; Obnam2 will use
This document uses some specific terminology related to backups. Here
is a glossary of such terms.
-* **chunk** is a relatively small amount of live data or metadata
+* a **chunk** is a relatively small amount of live data or metadata
about live data, as chosen by the client
-* **client** is the computer system where the live data lives, also the part of
- Obnam2 running on that computer
-* **generation** is a snapshot of live data
+* a **client** is the computer system where the live data lives, also
+ the part of Obnam running on that computer
+* a **generation** is a snapshot of live data, also known as **a
+ backup**
* **live data** is the data that gets backed up
-* **repository** is where the backups get stored
-* **server** is the computer system where the repository resides, also
- the part of Obnam2 running on that computer
+* a **repository** is where the backups get stored
+* a **server** is the computer system where the repository resides,
+ also the part of Obnam running on that computer
# Requirements