Merge branch 'read_me_small_fixes' into 'main'

remove r, change _ninja to _build

See merge request !883

README.md

@@ -120,7 +120,7 @@ That file-writer will switch to a new topic specified via start message. It will
 writing to that topic. The request to stop writing will also come to that topic.
 Once the file-writer has finished writing it will disconnect from the topic and return to the job pool topic.
 
-Note: all file-writers belong to the same consumer group, so only one will consumer the start message.
+Note: all file-writers belong to the same consumer group, so only one will consume the start message.
 
 This [flow-chart](documentation/file-writer-command-handler-state-machine.png) shows this information pictorially.
 

integration-tests/README.md

@@ -19,7 +19,7 @@ docker exec kafka bash -c "kafka-topics --bootstrap-server localhost:9092 --crea
 ```
 - Run the following command:
 ```
-pytest -s --file-writer-binary=../_ninja/bin/kafka-to-nexus 
+pytest -s --file-writer-binary=../_build/bin/kafka-to-nexus 
 ```
 ### Running locally without Docker
 Can be more convenient as Kafka remains running between tests runs, so other tools can be used to probe data.
@@ -30,5 +30,5 @@ Also, it is a bit quicker as it doesn't have to wait for Docker and Kafka to sta
 - Create the topics listed in the `topics.txt` file
 - Run the following command with appropriate Kafka address:
 ```
-pytest -s --file-writer-binary=../_ninja/bin/kafka-to-nexus --kafka-broker=localhost:9092
+pytest -s --file-writer-binary=../_build/bin/kafka-to-nexus --kafka-broker=localhost:9092
 ```
\ No newline at end of file