summaryrefslogtreecommitdiff
path: root/docs/repository-management.md
diff options
context:
space:
mode:
authorKelvin Fan <kfan@redhat.com>2020-10-15 19:51:44 -0400
committerKelvin Fan <kfan@redhat.com>2020-10-19 10:55:49 -0400
commita89d011c0b4ce73f4b48e1563ca7044cdfa9e0eb (patch)
tree5afa47cf212cefa188505737bccb53841e5e378b /docs/repository-management.md
parenta13509ee7d585047357f5ad3db1f3851e7400fb1 (diff)
downloadostree-a89d011c0b4ce73f4b48e1563ca7044cdfa9e0eb.tar.gz
docs: Fix various typos
Diffstat (limited to 'docs/repository-management.md')
-rw-r--r--docs/repository-management.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/repository-management.md b/docs/repository-management.md
index 11fe2f40..41b8d2b1 100644
--- a/docs/repository-management.md
+++ b/docs/repository-management.md
@@ -106,8 +106,7 @@ want to "promote" that commit. Let's create a new branch called
complete system. This might be where human testers get involved, for
example.
-A basic way to "promote" the `buildmaster` commit that passed
-testing like this:
+This is a basic way to "promote" the `buildmaster` commit that passed testing:
```
ostree commit -b exampleos/x86_64/smoketested/standard -s 'Passed tests' --tree=ref=aec070645fe53...