From e81aabba8c4e7c1e773b566f7229d5a3a3d82619 Mon Sep 17 00:00:00 2001 From: Giuseppe Scrivano Date: Thu, 7 Apr 2016 10:13:45 +0200 Subject: [PATCH] docs: Prefer the form "cannot" to "can not" Signed-off-by: Giuseppe Scrivano Closes: #242 Approved by: cgwalters --- docs/manual/related-projects.md | 2 +- docs/manual/repository-management.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/manual/related-projects.md b/docs/manual/related-projects.md index b53ba792..73972330 100644 --- a/docs/manual/related-projects.md +++ b/docs/manual/related-projects.md @@ -63,7 +63,7 @@ awareness of BTRFS in dpkg/rpm itself) will be required. The OSTree author believes that having total freedom at the block storage layer is better for general purpose operating systems. For example, with OSTree, one is free to use BTRFS in any way you like - -you can use a subvolume for `/home`, or you can not. +you can use a subvolume for `/home`, or you cannot. Furthermore, in its most basic incarnation, the rpm/dpkg + BTRFS doesn't solve the race conditions that happen when unpacking packages diff --git a/docs/manual/repository-management.md b/docs/manual/repository-management.md index ceb96cad..b83f6c15 100644 --- a/docs/manual/repository-management.md +++ b/docs/manual/repository-management.md @@ -179,7 +179,7 @@ you should update the summary file: ostree --repo=repo-prod summary -u ``` -(Remember, the `summary` command can not be run concurrently, so this +(Remember, the `summary` command cannot be run concurrently, so this should be triggered serially by other jobs). There is some more information on the design of the summary file in