aboutsummaryrefslogtreecommitdiff
path: root/bdep/init.cli
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2018-05-07 14:31:58 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2018-05-07 14:31:58 +0200
commit5a8bc87a5b355a1b9df503ef5dc48f8374fffae3 (patch)
treebf09f527c53e91e4db53d88b543c8083db49c9e8 /bdep/init.cli
parent0b2f299cd3a9db3744a79ca71edb793f5686f236 (diff)
Proofreading changes
Diffstat (limited to 'bdep/init.cli')
-rw-r--r--bdep/init.cli6
1 files changed, 3 insertions, 3 deletions
diff --git a/bdep/init.cli b/bdep/init.cli
index 57b1abb..0f0e882 100644
--- a/bdep/init.cli
+++ b/bdep/init.cli
@@ -51,8 +51,8 @@ namespace bdep
form.
The third (\cb{--config-add}) and fourth (\cb{--config-create}) forms are
- shortcuts that can be used to first add an existing or newly created
- build configuration and then initialize project packages in that
+ shortcuts to first adding an existing or newly created build
+ configuration and then initializing project packages in that
configuration. Semantically they are equivalent to first performing the
\cb{config add} or \cb{config create} commands (\l{bdep-config(1)}),
respectively, followed by the first form. Optional <cfg-args> in the
@@ -73,7 +73,7 @@ namespace bdep
The following invocations illustrate the common \cb{init} use cases (the
current working directory is shown before the shell prompt).
- Create new build configuration in \cb{../prj-gcc}, call it \cb{gcc} and
+ Create new build configuration in \cb{../prj-gcc}, call it \cb{gcc}, and
initialize project packages \cb{foo} and \cb{libfoo} in this
configuration: