openstack/nova-specs
Code Issues Proposed changes

Remove spurious blank lines from templates

Browse Source 
Clearly it doesn't make sense to have a blank line in the middle of a
paragraph.

Change-Id: I962c8abdd8a3e73291c5863bb2b4b96d458c58d0
Signed-off-by: Adam Spiers <aspiers@suse.com>
This commit is contained in:
Adam Spiers
2016-06-28 12:04:26 +01:00
parent 006108fb3c
commit a7d0871356
5 changed files with 0 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
specs/kilo-template.rst
View File

@@ -27,7 +27,6 @@ Some notes about the nova-spec and blueprint process:
* This is not intended to be extensive documentation for a new feature. * This is not intended to be extensive documentation for a new feature.
For example, there is no need to specify the exact configuration changes, For example, there is no need to specify the exact configuration changes,
nor the exact details of any DB model changes. But you should still define nor the exact details of any DB model changes. But you should still define
that such changes are required, and be clear on how that will affect that such changes are required, and be clear on how that will affect
upgrades. upgrades.

1
specs/liberty-template.rst
View File

@@ -27,7 +27,6 @@ Some notes about the nova-spec and blueprint process:
* This is not intended to be extensive documentation for a new feature. * This is not intended to be extensive documentation for a new feature.
For example, there is no need to specify the exact configuration changes, For example, there is no need to specify the exact configuration changes,
nor the exact details of any DB model changes. But you should still define nor the exact details of any DB model changes. But you should still define
that such changes are required, and be clear on how that will affect that such changes are required, and be clear on how that will affect
upgrades. upgrades.

1
specs/mitaka-template.rst
View File

@@ -27,7 +27,6 @@ Some notes about the nova-spec and blueprint process:
* This is not intended to be extensive documentation for a new feature. * This is not intended to be extensive documentation for a new feature.
For example, there is no need to specify the exact configuration changes, For example, there is no need to specify the exact configuration changes,
nor the exact details of any DB model changes. But you should still define nor the exact details of any DB model changes. But you should still define
that such changes are required, and be clear on how that will affect that such changes are required, and be clear on how that will affect
upgrades. upgrades.

1
specs/newton-template.rst
View File

@@ -27,7 +27,6 @@ Some notes about the nova-spec and blueprint process:
* This is not intended to be extensive documentation for a new feature. * This is not intended to be extensive documentation for a new feature.
For example, there is no need to specify the exact configuration changes, For example, there is no need to specify the exact configuration changes,
nor the exact details of any DB model changes. But you should still define nor the exact details of any DB model changes. But you should still define
that such changes are required, and be clear on how that will affect that such changes are required, and be clear on how that will affect
upgrades. upgrades.

1
specs/ocata-template.rst
View File

@@ -27,7 +27,6 @@ Some notes about the nova-spec and blueprint process:
* This is not intended to be extensive documentation for a new feature. * This is not intended to be extensive documentation for a new feature.
For example, there is no need to specify the exact configuration changes, For example, there is no need to specify the exact configuration changes,
nor the exact details of any DB model changes. But you should still define nor the exact details of any DB model changes. But you should still define
that such changes are required, and be clear on how that will affect that such changes are required, and be clear on how that will affect
upgrades. upgrades.