From baf6ba06be7d15f8b2a735b55fcdffb0dfc7b328 Mon Sep 17 00:00:00 2001 From: nevvermind Date: Wed, 27 May 2015 20:02:06 +0100 Subject: [PATCH] Update 02-libraries.md Small copy text fix. --- doc/02-libraries.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/02-libraries.md b/doc/02-libraries.md index 913f996b7..fa768be0c 100644 --- a/doc/02-libraries.md +++ b/doc/02-libraries.md @@ -96,9 +96,9 @@ Here are a few examples of valid tag names: ### Branches For every branch, a package development version will be created. If the branch -name looks like a version, the version will be `{branchname}-dev`. For example -a branch `2.0` will get a version `2.0.x-dev` (the `.x` is added for technical -reasons, to make sure it is recognized as a branch, a `2.0.x` branch would also +name looks like a version, the version will be `{branchname}-dev`. For example, +the branch `2.0` will get the `2.0.x-dev` version (the `.x` is added for technical +reasons, to make sure it is recognized as a branch). The `2.0.x` branch would also be valid and be turned into `2.0.x-dev` as well. If the branch does not look like a version, it will be `dev-{branchname}`. `master` results in a `dev-master` version.