Fix the order of code examples

Author: kosh-b

content/microservices/kafka.md

@@ -313,18 +313,16 @@ To access the original Kafka `IncomingMessage` object, use the `getMessage()` me
 ```typescript
 @@filename()
 @MessagePattern('hero.kill.dragon')
-async killDragon(@Payload() message: KillDragonMessage, @Ctx() context: KafkaContext) {
+killDragon(@Payload() message: KillDragonMessage, @Ctx() context: KafkaContext) {
   const originalMessage = context.getMessage();
-  const heartbeat = context.getHeartbeat();
-  
-  // Do some slow processing:
-  await doWorkPart1();
-
-  // Send heartbeat when it's possible in order to not exceed the sessionTimeout
-  await heartbeat();
-
-  // Do some slow processing again:
-  await doWorkPart2();
+  const { headers, partition, timestamp } = originalMessage;
+}
+@@switch
+@Bind(Payload(), Ctx())
+@MessagePattern('hero.kill.dragon')
+killDragon(message, context) {
+  const originalMessage = context.getMessage();
+  const { headers, partition, timestamp } = originalMessage;
 }
 ```
 
@@ -349,21 +347,22 @@ If your endpoint involves slow processing time for each message you should consi
 ```typescript
 @@filename()
 @MessagePattern('hero.kill.dragon')
-killDragon(@Payload() message: KillDragonMessage, @Ctx() context: KafkaContext) {
-  const originalMessage = context.getMessage();
-  const { headers, partition, timestamp } = originalMessage;
-}
-@@switch
-@Bind(Payload(), Ctx())
-@MessagePattern('hero.kill.dragon')
-killDragon(message, context) {
+async killDragon(@Payload() message: KillDragonMessage, @Ctx() context: KafkaContext) {
   const originalMessage = context.getMessage();
-  const { headers, partition, timestamp } = originalMessage;
+  const heartbeat = context.getHeartbeat();
+  
+  // Do some slow processing:
+  await doWorkPart1();
+
+  // Send heartbeat when it's possible in order to not exceed the sessionTimeout
+  await heartbeat();
+
+  // Do some slow processing again:
+  await doWorkPart2();
 }
 ```
 
 
-
 #### Naming conventions
 
 The Kafka microservice components append a description of their respective role onto the `client.clientId` and `consumer.groupId` options to prevent collisions between Nest microservice client and server components. By default the `ClientKafka` components append `-client` and the `ServerKafka` components append `-server` to both of these options. Note how the provided values below are transformed in that way (as shown in the comments).