Address review findings

Signed-off-by: Sebastian Schildt <[email protected]>

kuksa-client/README.md

@@ -27,12 +27,7 @@ After you have installed the kuksa-client package via pip you can run the test c
 $ kuksa-client
 ```
 
-With default CLI arguments, the client will try to connect to a local databroker, e.g. a server supporting the `kuksa.val.v1` protocol..
-If you wish to connect to a VISS server e.g. `kuksa-val-server`, you should instead run:
-
-```console
-$ kuksa-client ws://127.0.0.1:8090
-```
+With default CLI arguments, the client will try to connect to a local Databroker, e.g. a server supporting the `kuksa.val.v1` protocol without using TLS.
 
 If everything works as expected and the server can be contacted you will get an output similar to below.
 
@@ -55,14 +50,20 @@ Welcome to Kuksa Client version <some_version>
 
 Default tokens directory: /some/path/kuksa_certificates/jwt
 
-Connecting to VSS server at 127.0.0.1 port 55556 using KUKSA GRPC protocol.
+Connecting to VSS server at 127.0.0.1 port 55555 using KUKSA GRPC protocol.
 TLS will not be used.
 INFO 2023-09-15 18:48:13,415 kuksa_client.grpc No Root CA present, it will not be posible to use a secure connection!
 INFO 2023-09-15 18:48:13,415 kuksa_client.grpc.aio Establishing insecure channel
 gRPC channel connected.
 Test Client>
 ```
 
+If you wish to connect to a VISS server e.g. `kuksa-val-server` (not using TLS), you should instead run:
+
+```console
+$ kuksa-client ws://127.0.0.1:8090
+```
+
 If the connected KUKSA Server or KUKSA Databroker require authorization the next step is to authorize.
 KUKSA Server and KUKSA Databroker use different token formats.