[All addons] Review all readme.md files for V3 changes. (#9439)

Signed-off-by: Matthew Skinner <matt@pcmus.com>

* modbus.e3dc: newlines added and remove broken anchor.

Signed-off-by: Matthew Skinner <matt@pcmus.com>

* modbus.stie..:remove multiple newlines.

Signed-off-by: Matthew Skinner <matt@pcmus.com>

* modbus.sunspec: remove multiple newlines.


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Nanoleaf: remove PaperUI.


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Neato: Remove openhab 2


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Nibe: remove PaperUI.


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* NibeUplink: Remove PaperUI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Niko: Remove PaperUI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Nuki: Remove Paper UI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* OneWire: Remove multiple newlines.


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* OpenUV: remove paperui


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* OpenWebNet: Remove paperUI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Pentair: remove openhab2 path


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Fix typo


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* RFXCOM: remove PaperUI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Russound: Remove PaperUI.


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Samsung: remove paperui


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Siemens: remove paperui


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Samsung Smartthings: remove openhab 2 mention.


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Somfy myLink: remove paperUI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Somfy Tahoma: remove paperUI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Sonos: Remove paperui ref


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Spotify: remove paperui


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Tankerkönig: remove java8 and paperUI references.


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Tellstick: remove paperui


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Tibber: remove paperui


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Velbus: remove paperUI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Vitotronic: remove paperui


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* VolvoOnCall: remove paperUI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* WiFi LED: remove paperui


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* WlanThermo: remove paperUI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* XmlTV: remove openhab2 path


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Z-Way: Remove paperUI


Signed-off-by: Matthew Skinner <matt@pcmus.com>

* Update bundles/org.openhab.binding.nanoleaf/README.md

Signed-off-by: Matthew Skinner <matt@pcmus.com>

Co-authored-by: Fabian Wolter <github@fabian-wolter.de>

* MagentaTV: Fix typo

Signed-off-by: Matthew Skinner <matt@pcmus.com>

* MagentaTV: Change to userId


Signed-off-by: Matthew Skinner <matt@pcmus.com>

Co-authored-by: Fabian Wolter <github@fabian-wolter.de>

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

@@ -20,7 +20,7 @@ Follow instructions under:
 When registering your new Spotify Application for openHAB Spotify Bridge you have to specify the allowed "Redirect URIs" aka white-listed addresses.
 Here you have to specify the URL to the Bridge Authorization Servlet on your server.
 
-For example if you run your openHAB server on `http://openhabianpi:8080` you should add [http://openhabianpi:8080/connectspotify](http://openhabianpi:8080/connectspotify) as the redirect URIs.
+For example if you run your openHAB server on `http://openhab:8080` you should add [http://openhab:8080/connectspotify](http://openhab:8080/connectspotify) as the redirect URIs.
 
 This is important since the authorize process with Spotify takes place using your client web browser and Spotify will have to know the right URLs to your openHAB server for the authorization to be completed.
 When you have authorized with Spotify, this Redirect URI is where authorization tokens for your openHAB Spotify Brigde will be sent and they have to be received by the servlet on `/connectspotify`.
@@ -30,13 +30,13 @@ When you have authorized with Spotify, this Redirect URI is where authorization
 1. Install the binding and make sure the _Spotify Binding_ is listed on your server
 1. Complete the Spotify Application Registation if you have not already done so, see above.
 1. Make sure you have your Spotify Application _Client ID_ and _Client Secret_ identities available.
-1. Go to to your preferred openHAB admin UI and add a new Thing. Select the **"Spotify Player Bridge"**. Choose new Id for the player, unless you like the generated one, put in the _Client ID_ and _Client Secret_ from the Spotify Application registration in their respective fields of the bridge configuration. You can leave the _refreshPeriod_ as is. Save the bridge.
+1. Add a new **"Spotify Player Bridge"** thing. Choose new Id for the player, unless you like the generated one, put in the _Client ID_ and _Client Secret_ from the Spotify Application registration in their respective fields of the bridge configuration. You can leave the _refreshPeriod_ as is. Save the bridge.
 1. The bridge thing will stay in state _INITIALIZING_ and eventually go _OFFLINE_ - this is fine. You have to authorize this bridge with Spotify.
 1. Go to the authorization page of your server. `http://<your openHAB address>:8080/connectspotify`. Your newly added bridge should be listed there.
 1. Press the _"Authorize Player"_ button. This will take you either to the login page of Spotify or directly to the authorization screen. Login and/or authorize the application. If the Redirect URIs are correct you will be returned and the entry should show you are authorized with you Spotify user name/id. If not, go back to your Spotify Application and ensure you have the right Redirect URIs.
 1. The binding will be updated with a refresh token and go _ONLINE_. The refresh token is used to re-authorize the bridge with Spotify Connect Web API whenever required.
 
-Now that you have got your bridge _ONLINE_ it is time to discover your devices! Go to Paper UI Inbox and search for Spotify Connect Devices. Any device currently available on your account should show up immediately.
+Now that you have got your bridge _ONLINE_ you can now start a scan with the binding to auto discover your devices.
 
 If no devices show up you can start Spotify App on your PC/Mac/iOS/Android and start playing on your devices as you run discovery.
 This should make any Spotify Connect devices and Spotify Apps discoverable.