Standardize section header capitalization
Only capitalize the first word in each section header because that is what most sections already do. Change-Id: Id02b17cddba468567e32267bd5d463b2467b43b8
This commit is contained in:
parent
46e832ada7
commit
430d04efeb
@ -130,7 +130,7 @@ additionaProperties should be False).
|
||||
Reuse of existing predefined parameter types such as regexps for
|
||||
passwords and user defined names is highly encouraged.
|
||||
|
||||
Security Impact
|
||||
Security impact
|
||||
---------------
|
||||
|
||||
Describe any potential security impact on the system. Some of the items to
|
||||
@ -166,7 +166,7 @@ Notifications impact
|
||||
Please specify any changes to notifications. Be that an extra notification,
|
||||
changes to an existing notification, or removing a notification.
|
||||
|
||||
Other End user impact
|
||||
Other end user impact
|
||||
---------------------
|
||||
|
||||
Aside from the API, are there other ways a user will interact with this feature?
|
||||
@ -199,7 +199,7 @@ Examples of things to consider here include:
|
||||
* Will the change include any locking, and if so what considerations are there on
|
||||
holding the lock?
|
||||
|
||||
Other Deployer impact
|
||||
Other deployer impact
|
||||
---------------------
|
||||
|
||||
Discuss things that will affect how you deploy and configure OpenStack
|
||||
|
Loading…
x
Reference in New Issue
Block a user