update help message for getblockheader and getblock

[spiritlcx]

---

Thanks for contributing! Here are some hints how to create a great pull request:

• Follow the guidelines from https://github.com/dtr-org/unit-e/blob/master/CONTRIBUTING.md
• Make sure unit tests are green. Run them with make check.
• Make sure functional tests are green. Run them with test/functional/test_runner.py.
• Adapt documentation if affected by the pull request
• Sign your work (see https://github.com/dtr-org/unit-e/blob/master/CONTRIBUTING.md#sign-your-work)
• Add a summary of your changes and any additional context which is not in the commit messages to the description of the pull request (you are editing this right now ;-)
• Reference issues the pull request addresses, e.g. by adding a line `Fixes

  123`.

[castarco]

Hi @spiritlcx :) , thank you for contributing this PR.

I would like to point some minor issues:

• Please, write a description for the PR (feel free to replace the text that was there by default).
• For some reasons (see https://github.com/dtr-org/unit-e/blob/master/CONTRIBUTING.md ), we consider a requirement to add the "Signed-off by: YourNameHere" text to the commit messages & PR descriptions. You can easily amend your commit message and do a git push --force to your branch to fix this.

Cheers!

[spiritlcx]

Hi @spiritlcx :) , thank you for contributing this PR.

I would like to point some minor issues:

• Please, write a description for the PR (feel free to replace the text that was there by default).
• For some reasons (see https://github.com/dtr-org/unit-e/blob/master/CONTRIBUTING.md ), we consider a requirement to add the "Signed-off by: YourNameHere" text to the commit messages & PR descriptions. You can easily amend your commit message and do a git push --force to your branch to fix this.

Cheers!

Hi @castarco , thanks very much for the comments. I have reviewed the workflow and make some changes and made a new pull request https://github.com/dtr-org/unit-e/pull/1028 .

Cheers!