f

CONTRIBUTING.md

@@ -4,15 +4,13 @@ New contributions are welcomed. Follow this guide if you want to make one.
 
 ## Make a pull request
 
-Follow [Github guide](https://help.github.com/articles/creating-a-pull-request) to fork a repo
-and create a pull request.
+Follow [Github guide](https://help.github.com/articles/creating-a-pull-request) to fork a repo and create a pull request.
 
 All bug fixes and new features should go to the [`master`](https://github.com/rakutentech/docpub/tree/master) branch.
 
 ## Commit messages
 
-Commit messages should follow [conventional changelog
-standard](https://github.com/bcoe/conventional-changelog-standard/blob/master/convention.md).
+Commit messages should follow [conventional changelog standard](https://github.com/bcoe/conventional-changelog-standard/blob/master/convention.md).
 
 ## Code style and static analysis
 
@@ -31,8 +29,7 @@ Make sure all tests are passing before submitting pull request:
 npm test
 ```
 
-If you are fixing the bug, add a test that fails without your patch and passes with it. If you are
-adding a feature, write a test for it. To see test coverage report run:
+If you are fixing the bug, add a test that fails without your patch and passes with it. If you are adding a feature, write a test for it. To see test coverage report run:
 
 ```
 npm test --coverage

ISSUE_TEMPLATE.md

@@ -5,7 +5,7 @@ Output of `docpub --version`:
 
 ...
 
-Contents of `docpub.config` file:
+Contents of `docpub.config` file (if you have ZenDesk credentials declared in config, please strip it before):
 
 ```json