Apply suggestions from code review

Co-authored-by: Sergio Moya <[email protected]>
asyncapi · Feb 21, 2024 · 92d61c3 · 92d61c3
1 parent 45be13d
commit 92d61c3
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/100-level-AsyncAPI-Intro/step2.md b/100-level-AsyncAPI-Intro/step2.md
@@ -30,11 +30,11 @@ servers:
 
 - **Channels**
 
-The spaceship's radio stations, which correspond to specific topics like communicating with Capuccinova, are similar to the `channels` in AsyncAPI. These channels represent paths for sending specific types of messages. Each channel uses an address, which is a template for the URL of the server, and can have variables inside curly braces.
+The spaceship's radio stations, which correspond to specific topics like communicating with Capuccinova, are similar to the `channels` in AsyncAPI. These channels represent paths for sending specific types of messages. Each channel uses an address, which is a template for the URL of the server, and can have parameters inside curly braces that can be replaced dynamically at runtime.
 
 ```yml
 channels:
-  roomidchat:
+  chatRoom:
     address: chat/{roomId}
     messages:
       chatMessage:
@@ -92,7 +92,7 @@ components:
 
 - **Operations**
 
-`Operations` in AsyncAPI are like the instructions for the spaceship. They define what actions can be performed within each channel, such as sending or receiving messages. Each operation is associated with a message and a schema.
+`Operations` in AsyncAPI are like the instructions for the spaceship. They define what actions can be performed within each channel, such as sending or receiving messages. Each operation is associated with a channel and its messages.
 
 ```yml
 operations: