Fix formatting issues in course-definition.yml for consistency and clarity.

Author: rohitpaulk

course-definition.yml

@@ -141,7 +141,7 @@ stages:
       $ ./your_program.sh
       ```
 
-      It'll then try to connect to your server on port 9092 and send a `APIVersions-V3` request. The tester will validate that the correlation ID in the response header matches 
+      It'll then try to connect to your server on port 9092 and send a `APIVersions-V3` request. The tester will validate that the correlation ID in the response header matches
       the correlation ID in the request header.
 
       Although your server's response will need to contain the "message length" field (an int32), the tester will not verify this value in this stage.
@@ -164,10 +164,10 @@ stages:
       ```
 
       It'll then connect to your server on port 9092 and send a `APIVersions:V3` request with an invalid `APIVersion` of -1.
-      The tester will validate that the correlation ID in the response header matches 
+      The tester will validate that the correlation ID in the response header matches
       the correlation ID in the request header. The tester will also validate that the error code in the response body is 35.
       This is the error code for `UNSUPPORTED_VERSION`.
-      We are intentionally triggering this error to test that your server is correctly populating the error code in the response body. 
+      We are intentionally triggering this error to test that your server is correctly populating the error code in the response body.
 
       Although your server's response will need to contain the "message length" field (an int32), the tester will not verify this value in this stage.
 
@@ -198,7 +198,7 @@ stages:
       And that the `MaxVersion` for the `ApiKey` `18` is atleast `3`.
 
       ### Notes
-      - From this stage onwards, we expect you to send well formed responses. The total response length should be prefixed to your response, and we will only read that many bytes. 
+      - From this stage onwards, we expect you to send well formed responses. The total response length should be prefixed to your response, and we will only read that many bytes.
       - If extra bytes are remaining after decoding all the fields of the response body, it will be an error.
       - You can expect to receive V3 of the APIVersions request, and also send V3 of the APIVersions response.
 
@@ -245,7 +245,7 @@ stages:
       $ ./your_program.sh
       ```
 
-      It'll then connect to your server on port 9092 and send a `Fetch:V16` request. The tester will validate that the correlation ID in the response header matches 
+      It'll then connect to your server on port 9092 and send a `Fetch:V16` request. The tester will validate that the correlation ID in the response header matches
       the correlation ID in the request header. The tester will also validate that the error code in the response body is 0.
       Then, it will validate that the response body contains no topicResponses. (But as the response body contains COMPACT_ARRAY of topicResponses, the length should be prefixed as 1).
       The hexdump of a sample kafka response for this request is given below.
@@ -275,15 +275,15 @@ stages:
       $ ./your_program.sh
       ```
 
-      It'll then connect to your server on port 9092 and send a `Fetch:V16` request. The tester will validate that the correlation ID in the response header matches 
+      It'll then connect to your server on port 9092 and send a `Fetch:V16` request. The tester will validate that the correlation ID in the response header matches
       the correlation ID in the request header. The tester will also validate that the error code in the response body is 0.
       Then, it will validate that the response body contains a topicResponse for the topic provided in the request.
       And that the topicResponse contains a partitionResponse for the partition provided in the request.
 
       The partitionResponse should contain a messageSet with a RecordBatch.
-      Which should in turn contain a Record which should contain a string with the hardcoded message. 
+      Which should in turn contain a Record which should contain a string with the hardcoded message.
 
-      You need to send 3 such messages in the response. 
+      You need to send 3 such messages in the response.
       The messages should be `m1, m2, m3`.
 
       The RecordBatch has a CRC field, which is computed using the Castagnoli polynomial. This CRC field in the response should match with the CRC computed from the RecordBatch contents.