fixup! Example AWS Lambda function, triggered by the Reactor, that publishes another message back to Ably

Author: franrob-projects

src/pages/docs/platform/integrations/webhooks/lambda.mdx

@@ -113,17 +113,17 @@ Lambda functions might run multiple times for the same Ably event. Design functi
 
 You can configure retry behavior in your AWS Lambda console under the function's asynchronous invocation settings. See the [AWS Lambda documentation](https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html#invocation-async-errors) for details on adjusting retry settings.
 
-## Routing Messages with Integration Rules <a id="routing"/>
+## Routing messages with integration Rules <a id="routing"/>
 
 When an Integration Rule triggers your Lambda function, it can process the incoming message and publish a response back to Ably. This enables message routing and transformation patterns across your channels.
 
-### Lambda Function Setup
+### Lambda Function setup
 
-Your Lambda function must be packaged with the Ably client library and uploaded to AWS Lambda as a zip file.
+Your Lambda Function must be packaged with the Ably SDK and uploaded to AWS Lambda as a zip file.
 
-For a complete example package, see: https://github.com/ably/example-lambda-function
+Uses `Ably.Rest` instead of `Ably.Realtime` because REST API is more efficient for one-off publishing operations and avoids WebSocket connection overhead in Lambda's stateless environment.
 
-### Implementation
+The following example shows an AWS Lambda function that receives Ably events and publishes responses back to an Ably channel:
 
 <Code>
 ```javascript
@@ -163,9 +163,3 @@ exports.handler = (event, context, callback) => {
 };
 ```
 </Code>
-
-### Important Considerations
-
-**Avoiding Infinite Loops**: Never publish messages to a channel that would trigger the same Integration Rule. Always ensure your target channel is different from the source channel or configure your Integration Rule with appropriate channel filters.
-
-**Using REST vs. Realtime**: The example uses `Ably.Rest` instead of `Ably.Realtime` because REST API is more efficient for one-off publishing operations and avoids WebSocket connection overhead in Lambda's stateless environment.