Description of your changes

This PR aims at addressing some of the early feedback for the documentation:

• Fixes Docs: Syntax typo on within Connect sub-section #358
• Fixes Docs: clarify Middy's role #359
• Fixes Docs: Improve contrast in source code expressions for low-eyesight  #360
• Fixes Docs: Move Patching under Getting Started #361
• Fixes Docs: Inconsistent navigation to demonstrate multi-approach to capture Lambda context info #362

How to verify this change

Checkout docs/all_clarifications branch & run npm run docs-runLocalDocker.

Highlights:

#360

Before:

After: The inline code is now bolder & improves contrast

#359

Added note + tip regarding Middy under the first middleware code snippet of each utility:

#361

Moved "Patching AWS SDK clients" subsection under "Getting Started" section:

#362

Uniformed code example under "Capturing Lambda context info" subsection for Logger to use tabs like other utilities:

#363

Added a new section "Testing your code" under Logger to clarify that if Customers want to have the context info in their logs they need to pass a dummy context, added also a mention to the @aws-lambda-powertools/commons package that Customers can use in case they don't want to create their own dummy context.

For context: in the Python version of Powertools if no context object is passed then Logger will raise an exception. In the Typescript version instead Customers using Typescript must always pass an object of type Context as enforced by the type definition. With that said, if they choose to pass an empty object with type casting (i.e. {} as Context), or they are using Javascript without strong types, Logger still won't throw an error but simply log null as value of the keys related to the context.

Related issues, RFCs

#358
#359
#360
#361
#362
#363

PR status

Is this ready for review?: YES
Is it a breaking change?: NO

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• The code coverage hasn't decreased
• The PR title follows the conventional commit semantics

Breaking change checklist

N/A

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.