docs: remove todo style

Signed-off-by: heitorlessa <[email protected]>

Author: heitorlessa

docs/contributing/setup.md

@@ -24,16 +24,16 @@ graph LR
 
 Unless you're using the pre-configured Cloud environment, you'll need the following installed:
 
-* [x] [GitHub account](https://github.com/join){target="_blank" rel="nofollow"}. You'll need to be able to fork, clone, and contribute via pull request.
-* [x] [Python 3.8+](https://www.python.org/downloads/){target="_blank" rel="nofollow"}. Pick any version supported in [AWS Lambda runtime](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html).
-* [x] [Docker](https://docs.docker.com/engine/install/){target="_blank" rel="nofollow"}. We use it to run documentation linters and non-Python tooling.
-* [x] [Fork the repository](https://github.com/aws-powertools/powertools-lambda-python/fork). You'll work against your fork of this repository.
+* [GitHub account](https://github.com/join){target="_blank" rel="nofollow"}. You'll need to be able to fork, clone, and contribute via pull request.
+* [Python 3.8+](https://www.python.org/downloads/){target="_blank" rel="nofollow"}. Pick any version supported in [AWS Lambda runtime](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html).
+* [Docker](https://docs.docker.com/engine/install/){target="_blank" rel="nofollow"}. We use it to run documentation linters and non-Python tooling.
+* [Fork the repository](https://github.com/aws-powertools/powertools-lambda-python/fork). You'll work against your fork of this repository.
 
 ??? note "Additional requirements if running end-to-end tests"
 
-    * [x] [AWS CDK CLI](https://docs.aws.amazon.com/cdk/v2/guide/getting_started.html#getting_started_prerequisites){target="_blank"}
-    * [x] [AWS Account bootstrapped with CDK](https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping.html){target="_blank"}
-    * [x] [AWS CLI installed and configured](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
+    * [AWS CDK CLI](https://docs.aws.amazon.com/cdk/v2/guide/getting_started.html#getting_started_prerequisites){target="_blank"}
+    * [AWS Account bootstrapped with CDK](https://docs.aws.amazon.com/cdk/v2/guide/bootstrapping.html){target="_blank"}
+    * [AWS CLI installed and configured](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html)
 
 ## Cloud environment
 
@@ -65,23 +65,3 @@ You might find useful to run both the documentation website and the API referenc
 * **Docs website**: `make docs-local`
     * If you prefer using Docker: `make docs-local-docker`
 * **API reference**: `make docs-api-local`
-
-## Sending a pull request
-
-!!! note "First time creating a Pull Request? Keep [this document handy.](https://help.github.com/articles/creating-a-pull-request/){target='blank' rel='nofollow'}"
-
-Before sending us a pull request, please ensure that:
-
-1. You are working against the latest source on the **develop** branch.
-2. You check existing [open, and recently merged](https://github.com/aws-powertools/powertools-lambda-python/pulls?q=is%3Apr+is%3Aopen%2Cmerged+sort%3Aupdated-desc){target="_blank" rel="nofollow"} pull requests to make sure someone else hasn't addressed the problem already.
-3. You open an [issue](https://github.com/aws-powertools/powertools-lambda-python/issues/new/choose){target="_blank" rel="nofollow"} before you begin any implementation. We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.
-4. Create a new branch named after the change you are contributing _e.g._ `feat/logger-debug-sampling`
-
-**Ready?**
-
-These are the steps to send a pull request:
-
-1. Run all code quality, tests, and baseline checks: `make pr`
-2. Commit to your fork using clear commit messages. Don't worry about typos, we will squash all commits during merge.
-3. Send us a pull request with a [conventional semantic title](https://github.com/aws-powertools/powertools-lambda-python/pull/67). We prepared a set of questions you can answer in GitHub User Interface to make reviewing easier.
-4. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.