diff --git a/Json-service.md b/Json-service.md
index f1ebfb7..af292b6 100644
--- a/Json-service.md
+++ b/Json-service.md
@@ -1,4 +1,6 @@
-signal-cli (proposed release) supports a JSON RPC server that accepts input on STDIN and replies on STDOUT. See (https://github.com/AsamK/signal-cli/discussions/679)
+signal-cli (proposed release)  supports a JSON RPC server that accepts input on STDIN and replies on STDOUT. See (https://github.com/AsamK/signal-cli/discussions/679)
+
+    `signal-cli --output=json -u USERNAME jsonRpc`
 
 It is possible to communicate with the server over the network using named pipes. For example, the following command sets up  a JSON RPC signal-cli server listening on local port 9182:
 
@@ -7,7 +9,7 @@ It is possible to communicate with the server over the network using named pipes
 To communicate with the server from the same machine (localhost), issue the command:
 `nc localhost 9182`
 
-Enter your requests in the required format. Be sure to include the arbitrary "id" field if you want to receive a response! The response will contain the same "id" as its last field. For example:
+It will await your entries in the required format. Be sure to include the arbitrary "id" field if you want to receive a response! The response will contain the same "id" as its last field. For example:
 
 ENTRY: `{"jsonrpc":"2.0","method":"listGroups","id":"my special mark"}`