Fix Markdown warnings in README.md (#14187)

Signed-off-by: Holger Friedrich <mail@holger-friedrich.de>

bundles/org.openhab.automation.jrubyscripting/README.md

@@ -111,6 +111,7 @@ end
 ```
 
 #### weather.items
+
 ```Xtend
 Number:Angle Exterior_WindDirection "Wind Direction [SCRIPT(rb:compass.script):%s]" <wind>
 ```

bundles/org.openhab.binding.dwdunwetter/README.md

@@ -18,6 +18,7 @@ Each Thing provides one or more warnings for a city.
 | warningCount | 1       | No       | Number of warnings to provide.                                                                                                             |
 
 ### Cell ID
+
 <!-- See page 10-13 (in German) of https://www.dwd.de/DE/wetter/warnungen_aktuell/objekt_einbindung/einbindung_karten_geodienste.pdf?__blob=publicationFile&v=14 for Cell ID documentation. -->
 Use [this list](https://www.dwd.de/DE/leistungen/opendata/help/warnungen/cap_warncellids_csv.csv) of valid IDs, please notice that **only IDs starting with an eight (8) and nine digits are supported** by this binding.
 Exeception for Berlin, where the ID of the city's districts are used. Those start with a seven (7).

bundles/org.openhab.binding.sonyaudio/README.md

@@ -5,6 +5,7 @@ This binding integrates the [Sony Audio Control API](https://developer.sony.com/
 ## Supported Things
 
 For the moment the devices that are supported by this binding are
+
 - STR-DN1080
 - HT-CT800
 - SRS-ZR5

bundles/org.openhab.binding.tacmi/README.md

@@ -8,10 +8,12 @@ These modes are:
 
 
 Via a "Schema API Page"
+
   * Read values from output nodes
   * Change values for controllable nodes
 
 CoE (CAN over Ethernet) Connection
+
   * Receive data from analog CAN-outputs defined in TAPPS2
   * Receive data from digital CAN-outputs defined in TAPPS2
   * Send ON/OFF to digital CAN-inputs defined in TAPPS2

bundles/org.openhab.binding.teleinfo/README.md

@@ -153,6 +153,7 @@ The following channels are available on all Linky telemeters in standard TIC mod
 #### Three phase only channels
 
 These channels are available on the following telemeters:
+
 * lstm_electricitymeter
 * lsmt_prod_electricitymeter
 
@@ -171,6 +172,7 @@ These channels are available on the following telemeters:
 #### Producer only channels
 
 These channels are available on the following telemeters:
+
 * lsmm_prod_electricitymeter
 * lsmt_prod_electricitymeter
 

bundles/org.openhab.binding.wolfsmartset/README.md

@@ -80,6 +80,7 @@ Bridge wolfsmartset:account:account "Wolf Smartset Account" [ username="User", p
     }
 }
 ````
+
 _You need to use the corrosponding systemId and unitId returned by the discovery_
 
 ### Items

bundles/org.openhab.binding.yamahareceiver/README.md

@@ -205,6 +205,7 @@ String      Yamaha_Input_Ex
 The synthetic `Yamaha_Input_Ex` will be calculated by a rule (see below) and will drive sitemap visibility (see below).
 
 Rules:
+
 ```
 rule "Yamaha_Input_Ex"
 when
@@ -237,6 +238,7 @@ Notice how we have two preset mappings that each is meant for FM and DAB+ bands
 Enabling detailed logging may help troubleshoot your configuration (or trace bugs in the binding itself). 
 
 Add the following lines to the logger configuration file (`userdata\etc\org.ops4j.pax.logging.cfg`):
+
 ```
 log4j2.logger.yamaha.name = org.openhab.binding.yamahareceiver
 log4j2.logger.yamaha.level = TRACE

bundles/org.openhab.transform.jinja/README.md

@@ -33,6 +33,7 @@ the template
 extracts the string `4.7`.
 
 #### Outgoing data
+
 The JINJA transformation can be used to publish simple JSON strings through, for example, the HTTP Binding's `commandTransformation` parameter.
 
 Say we have a String Item which holds the following value:
@@ -52,6 +53,7 @@ will send the following string out of openHAB
 ```json
 {"msgtype":"m.text", "body":"This is my string"}
 ```
+
 `{{value}}` will be replaced by whatever the value of your Item is.
 
 Note that if using \*.things files you must escape quotation marks, for example:

bundles/org.openhab.transform.regex/README.md

@@ -45,6 +45,7 @@ Number  Temperature "Temperature [%.1f °C]"
 ```
 
 The regex pattern is is defined as follows
+
 * `.*` match any character, zero and unlimited times
 * `=` match the equal sign literally, used to find the position
 *  `()` capture group match 

bundles/org.openhab.transform.scale/README.md

@@ -22,26 +22,32 @@ These expressions are evaluated from top to bottom.
 The first range that includes the value is selected.
 
 ## Special entries
+
 Some special entries can be used in the scale file.
 
 ### Catchall Entry
+
 `[..]=Catchall`
 
 This entry will match all numeric values not met by a previous range. Obviously, this one should be put at the very end of the scale definition file.
 
 ### Not A Number
+
 Scale transform is designed to work with numeric or quantity states. When the value presented to scale transform does not match this (most of the time with NULL or UNDEF states) it will not be handled and a warning is raised in the openhab.log . This case can be smoothly avoided with a 
 
 `NaN=Non Numeric State presented`
 
 ### Formatting output
+
 At last, Scale transform can take care of formatting an output with this entry :
 
 `format=%label% (%value%) !`
 
 Where : 
+
 - `%label%` will be replaced by transformed value and 
 - `%value%` is the numeric value presen
+
 ## Example
 
 The following example shows how to break down numeric UV values into fixed UV index categories.

bundles/org.openhab.transform.xpath/README.md

@@ -47,10 +47,12 @@ Given a retrieved XML (e.g. from an HIK Vision device with the namespace `xmlns=
 A simple xpath query to fetch the Azimut value does not work as it does not address the namespace.
 
 There are two ways to address the namespace.
+
 * Simple path which may not work in complex XML.
 * With full qualified path.
-* 
+
 The XPath
+
 * `[name()='PTZStatus']/*[name()='AbsoluteHigh']/*[name()='azimuth']/`
 * `/*[local-name()='PTZStatus' and namespace-uri()='http://www.hikvision.com/ver20/XMLSchema']/*[local-name()='AbsoluteHigh' and namespace-uri()='http://www.hikvision.com/ver20/XMLSchema']/*[local-name()='azimuth' and namespace-uri()='http://www.hikvision.com/ver20/XMLSchema']`