aboutsummaryrefslogtreecommitdiff
path: root/doc/manual/src/design/store/relocatability.md
diff options
context:
space:
mode:
Diffstat (limited to 'doc/manual/src/design/store/relocatability.md')
-rw-r--r--doc/manual/src/design/store/relocatability.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/manual/src/design/store/relocatability.md b/doc/manual/src/design/store/relocatability.md
index 5cdbe9486..c7f869135 100644
--- a/doc/manual/src/design/store/relocatability.md
+++ b/doc/manual/src/design/store/relocatability.md
@@ -1,8 +1,8 @@
-## Advanced Topic: store object relocatability
+## Advanced Topic: Store object relocation
-Now that we know the fundamentals of the design of the Nix store, let's explore one consequence of that design: the question when it is permissable to relocate a store object to a store with a different mount point.
+Now that we know the fundamentals of the design of the Nix store, let's explore one consequence of that design: the question when it is permissible to relocate a store object to a store with a different mount point.
-Recall from the section on [store paths](./store-paths.md), concrete store paths look like `<store-dir>/<hash>-<name>`.
+Recall from the section on [store paths](./store-paths.md) that concrete store paths look like `<store-dir>/<hash>-<name>`.
~~The two final restrictions of the previous section yield an alternative view of the same information.~~
Rather than associating store dirs with the references, we can say a store object itself has a store dir if and only if it has at least one reference.