packaging
/
ostree
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: Prefer the form "cannot" to "can not" 

Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>

Closes: #242
Approved by: cgwalters
This commit is contained in:
Giuseppe Scrivano 2016-04-07 10:13:45 +02:00 committed by Colin Walters (automation)
parent 3152516ab3
commit e81aabba8c
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/manual/related-projects.md
View File

@ -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 The OSTree author believes that having total freedom at the block
storage layer is better for general purpose operating systems. For storage layer is better for general purpose operating systems. For
example, with OSTree, one is free to use BTRFS in any way you like - 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 Furthermore, in its most basic incarnation, the rpm/dpkg + BTRFS
doesn't solve the race conditions that happen when unpacking packages doesn't solve the race conditions that happen when unpacking packages

2
docs/manual/repository-management.md
View File

@ -179,7 +179,7 @@ you should update the summary file:
ostree --repo=repo-prod summary -u 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). should be triggered serially by other jobs).
There is some more information on the design of the summary file in There is some more information on the design of the summary file in