Remove spurious blank lines from templates
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:
parent
006108fb3c
commit
a7d0871356
|
@ -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.
|
||||
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
|
||||
that such changes are required, and be clear on how that will affect
|
||||
upgrades.
|
||||
|
|
|
@ -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.
|
||||
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
|
||||
that such changes are required, and be clear on how that will affect
|
||||
upgrades.
|
||||
|
|
|
@ -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.
|
||||
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
|
||||
that such changes are required, and be clear on how that will affect
|
||||
upgrades.
|
||||
|
|
|
@ -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.
|
||||
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
|
||||
that such changes are required, and be clear on how that will affect
|
||||
upgrades.
|
||||
|
|
|
@ -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.
|
||||
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
|
||||
that such changes are required, and be clear on how that will affect
|
||||
upgrades.
|
||||
|
|
Loading…
Reference in New Issue