WIP - Bash code review - first commit

aka - Wrap some long lines in README.md

This is just a benign first commit so that I can create a pull request
for this repository.

Per #208 I wish to code
review the Bash content and make suggestions on possible improvements.

I haven't done this before so I'm not sure of the best way to go about
it.
I'm thinking to use this pull request, where I will make a commit for
each suggestion with a couple of code changes to demonstrate the
objective.
Then we can can discuss it.

I don't expect the PR to be merged, but you might end up cherry-picking
some commits in it.

Let me know if this approach works for you and I'll start adding commits
soon after.

Author: ingydotnet

README.md

@@ -57,7 +57,8 @@ false matches of job failures unrelated to the specified ticket.
   example from progress.opensuse.org, label the job and retrigger if specified
   in the issue (see the source code for details how to mark tickets)
 
-For tickets referencing "auto_review" it is suggested to add a text section based on the following template:
+For tickets referencing "auto_review" it is suggested to add a text section
+based on the following template:
 
 ```
 ## Steps to reproduce
@@ -178,7 +179,9 @@ It will be automatically cloned.
     make checkstyle
 
 #### openqa-label-known-issues
-Generate a list of recent incomplete jobs of your local openQA instance. Here's an example using `psql`:
+
+Generate a list of recent incomplete jobs of your local openQA instance. Here's
+an example using `psql`:
 
 ```
 psql \