openstack
/
sahara
Code Issues Proposed changes

Changed the spelling mistake. 

Change-Id: Ia3a66a254554c9a206c8d5fb9a21179e21d899ee
This commit is contained in:
kavithahr 2017-02-23 17:32:16 +05:30 committed by kavitha h r
parent fbd43c3acf
commit 46b649450c
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
HACKING.rst
View File

@ -14,7 +14,7 @@ Using a common format for commit messages will help keep our git history
readable. Follow these guidelines:
- [S365] First, provide a brief summary of 50 characters or less. Summaries
of greater then 72 characters will be rejected by the gate.
of greater than 72 characters will be rejected by the gate.
- [S364] The first line of the commit message should provide an accurate
description of the change, not just a reference to a bug or blueprint.

4
doc/source/devref/development.guidelines.rst
View File

@ -20,12 +20,12 @@ To check your code against PEP 8 and bashate run:
Static analysis
---------------
The static analysis checks are optional in Sahara. but they are still very
The static analysis checks are optional in Sahara, but they are still very
useful. The gate job will inform you if the number of static analysis warnings
has increased after your change. We recommend to always check the static
warnings.
To run the check commit yor change first and execute the following command:
To run check first commit your change, then execute the following command:
.. sourcecode:: console