Addressing Ruben's feedback

Author: leandrodamascena

aws_lambda_powertools/utilities/batch/sqs_fifo_partial_processor.py

@@ -93,7 +93,7 @@ def process(self) -> List[Tuple]:
             # If we have failed messages and we are set to return on the first error,
             # short circuit the process and return the remaining messages as failed items
             if self.fail_messages and not self._skip_group_on_error:
-                logger.debug("Processing of failed messages stopped due to the 'skip_group_on_error' is set to False")
+                logger.debug("Processing of failed messages stopped because 'skip_group_on_error' is False")
                 return self._short_circuit_processing(i, result)
 
             msg_id = record.get("messageId")

docs/utilities/batch.md

@@ -141,7 +141,7 @@ Processing batches from SQS works in three stages:
 
 #### FIFO queues
 
-When working with [SQS FIFO queues](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html){target="_blank"}, you should know that a batch may include messages from different group IDs.
+When working with [SQS FIFO queues](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html){target="_blank"}, a batch may include messages from different group IDs.
 
 By default, we will stop processing at the first failure and mark unprocessed messages as failed to preserve ordering. However, this behavior may not be optimal for customers who wish to proceed with processing messages from a different group ID.