diff options
| author | Paul Moore <paul@paul-moore.com> | 2017-02-28 15:27:19 -0500 |
|---|---|---|
| committer | Paul Moore <paul@paul-moore.com> | 2017-02-28 15:27:19 -0500 |
| commit | fda1f0741fb55d6951f312f310cc159e17555788 (patch) | |
| tree | 06f492ab696308e8d0c14f6048623526924384c9 | |
| parent | a6c2af564633bc3b44ae89b6a0a8aa9d719b43a7 (diff) | |
| download | libseccomp-fda1f0741fb55d6951f312f310cc159e17555788.tar.gz | |
doc: fix some small typos in SUBMITTING_PATCHES
Signed-off-by: Paul Moore <paul@paul-moore.com>
| -rw-r--r-- | SUBMITTING_PATCHES.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/SUBMITTING_PATCHES.md b/SUBMITTING_PATCHES.md index c24e141..b3507fa 100644 --- a/SUBMITTING_PATCHES.md +++ b/SUBMITTING_PATCHES.md @@ -41,13 +41,13 @@ command: ## Make Sure Your Code is Tested The libseccomp code includes a fairly extensive test suite and any submissions -which add functionality or significantly change the existing code should +which add functionality, or significantly change the existing code, should include additional tests to verify the proper operation of the proposed changes. -Code coverage analysis tools has been integrated into the libseccomp code base, -and can be enabled via the "--enable-code-coverage" configure flag and the -"check-code-coverage" make target. Additional details on generating code +Code coverage analysis tools have been integrated into the libseccomp code +base, and can be enabled via the "--enable-code-coverage" configure flag and +the "check-code-coverage" make target. Additional details on generating code coverage information can be found in the .travis.yml file. ## Generate the Patch(es) |