Resolve "Make specification langauge more concise"

Closes #33 (closed)

pages/docs/using.md

@@ -5,9 +5,9 @@ The full example is available at <https://git-st.inf.tu-dresden.de/jastadd/ragco
 ## Preparation
 
 The following examples are inspired by the real test case [read1write2](https://git-st.inf.tu-dresden.de/jastadd/ragconnect-tests/-/tree/master/ragconnect.tests/src/test/01-input/read1write2)
-The idea is to have two nonterminals, where input information is received on one of them, and - after transformation - is sent out by both.
+The idea is to have two non-terminals, where input information is received on one of them, and - after transformation - is sent out by both.
 
-Let the following grammar be used:
+Let's use the following grammar:
 
 ```bnf
 A ::= <Input:String> /<OutputOnA:String>/ B* ;
@@ -92,7 +92,7 @@ b1.connectOutputOnB("mqtt://localhost/b1/out", true);
 b2.connectOutputOnB("mqtt://localhost/b2/out", false);
 ```
 
-The first parameter of those connect-methods is always an URI-like String, to identify the protocol to use, the server operating the protocol, and a path to identify the concrete token.
+The first parameter of those connect-methods is always a URI-like String, to identify the protocol to use, the server operating the protocol, and a path to identify the concrete token.
 In case of MQTT, the server is the host running an MQTT broker, and the path is equal to the topic to publish or subscribe to.
 Please note, that the first leading slash (`/`) is removed for MQTT topics, e.g., for `A.Input` the topic is actually `topic/for/input`.