From 7b21c122e25d153360974a23f13a02a8282ae39d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20Zapke-Gru=CC=88ndemann?= Date: Wed, 18 Sep 2013 09:35:36 +0200 Subject: [PATCH] Fixed a few typos. --- README.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.rst b/README.rst index b62c0d4..0fe9a77 100644 --- a/README.rst +++ b/README.rst @@ -38,9 +38,9 @@ Mimic the format seen `in Fabric's changelog * Create a docs file named ``changelog.rst`` with a top-level header followed by a bulleted list. -* Bullet list items must use the ``:support:``, ``:feature`` or ``:bug`` roles to - mark issues, or ``:release:`` to mark a release. These special roles must be - the first element in each list item. +* Bullet list items must use the ``:support:``, ``:feature:`` or ``:bug:`` + roles to mark issues, or ``:release:`` to mark a release. These special roles + must be the first element in each list item. * Issue roles are of the form ``:type:`number[ keyword]```. Keywords are optional and may be one of: @@ -97,8 +97,8 @@ TODO entry is not (IMHO) acceptable. * Possibly add more keywords to allow control over additional edge cases. -* Add shortcut format option for the release/issue URI settings - Github users - can just give their Github acct/repo and we will fill in the rest. +* Add shortcut format option for the release/issue URI settings - GitHub users + can just give their GitHub acct/repo and we will fill in the rest. * Maybe say pre-1.0 releases consider all bugs 'major' (so one can e.g. put out an 0.4.0 which is all bugfixes). Iffy because what if you *wanted* regular feature-vs-bugfix releases pre-1.0? (which is common.)