chore: fix contributing guide

apps/documentation/pages/contributing/index.mdx

@@ -1,22 +1,37 @@
 ---
 title: Contributing Guide
-description: Set up Documenso using Docker for local development.
+description: Learn how to contribute to Documenso and become part of our community.
 ---
 
-import { Callout } from 'nextra/components';
+import { Callout, Steps } from 'nextra/components';
 
 # Contributing to Documenso
 
 If you plan to contribute to Documenso, please take a moment to feel awesome ✨. People like you are what open source is about ♥. Any contributions, no matter how big or small, are highly appreciated 🙏. This guide will help you get started with contributing to Documenso 💻.
 
-## Before getting started
+## Before Getting Started
 
-- Search the existing [issues](https://github.com/documenso/documenso/issues) to see if someone else reported the same issue. Or, check the [existing PRs](https://github.com/documenso/documenso/pulls) to see if someone else is already working on the same thing.
-- If there is no issue or PR for the problem you are facing, feel free to create a new issue. Make sure to provide as much detail as possible, including the steps to reproduce the issue.
-- If you pick an existing issue, take into consideration the discussion on the issue.
-- Accept the [Contributor License Agreement](https://documen.so/cla) to ensure we can accept your contributions.
+<Steps>
 
-## Taking issues
+### Check the Existing Issues and Pull Requests
+
+Search the existing [issues](https://github.com/documenso/documenso/issues) to see if someone else reported the same issue. Or, check the [existing PRs](https://github.com/documenso/documenso/pulls) to see if someone else is already working on the same thing.
+
+### Creating a New Issue
+
+If there is no issue or PR for the problem you are facing, feel free to create a new issue. Make sure to provide as much detail as possible, including the steps to reproduce the issue.
+
+### Picking an Existing Issue
+
+If you pick an existing issue, take into consideration the discussion on the issue.
+
+### Contributor License Agreement
+
+Accept the [Contributor License Agreement](https://documen.so/cla) to ensure we can accept your contributions.
+
+</Steps>
+
+## Taking Issues
 
 Before taking an issue, ensure that:
 
@@ -34,16 +49,25 @@ Feel free to ask for help, clarification or guidance if needed. We are here to h
 
 ## Developing
 
-The development branch is <code>main</code>, and all pull requests should be made against this branch. Here's how you can get started with developing:
+The development branch is `main`, and all pull requests should be made against this branch. Here's how you can get started with developing:
 
-1. Fork the repository to your GitHub account and then
-   clone it to your local device.
+<Steps>
 
-2. Check out the [local development](/local-development) guide to set up your local environment.
+### Set Up Documenso Locally
 
-3. Find an issue to work on or create a new one.
+Check out the [local development](/local-development) guide to set up your local environment.
 
-4. Create a new branch for your feature or bug fix.
+### Pick a Task
+
+Find an issue to work on or create a new one.
+
+- Before starting to work on an issue, ensure that no one else is working on it. If no one is assigned to the issue, feel free to pick it up by leaving a comment on the issue and asking to get it assigned to you.
+
+Before creating a new issue, check the existing issues to see if someone else has already reported it.
+
+### Create a New Branch
+
+After you're assigned an issue, you can start working on it. Create a new branch for your feature or bug fix.
 
 When creating a branch, make sure that the branch name:
 
@@ -60,7 +84,15 @@ git checkout -b feat/1234-add-share-button-to-articles
 
 In the pull request description, include `references #yyyy` or `fixes #yyyy` to link it to the issue you are working on.
 
-4. Implement your changes.
+### Implement Your Changes
+
+Start working on the issue you picked up and implement the changes. Make sure to test your changes locally and ensure that they work as expected.
+
+### Open a Pull Request
+
+After implementing your changes, open a pull request against the `main` branch.
+
+</Steps>
 
 <Callout type="info">
   If you need help getting started, [join us on Discord](https://documen.so/discord).
@@ -68,9 +100,7 @@ In the pull request description, include `references #yyyy` or `fixes #yyyy` to
 
 ## Building
 
-Before pushing code or creating pull requests, please ensure you can successfully create a successful production build.
-
-You can build the project by running the following command in your terminal:
+Before pushing code or creating pull requests, please ensure you can successfully create a successful production build. You can build the project by running the following command in your terminal:
 
 ```bash
 npm run build
@@ -78,7 +108,7 @@ npm run build
 
 Once the project builds successfully, you can push your code changes or create a pull request.
 
-<Callout emoji="💡">
+<Callout type="info">
   Remember to run tests and perform any necessary checks before finalizing your changes. As a
   result, we can collaborate more effectively and maintain a high standard of code quality in our
   project.

apps/documentation/pages/public-api/authentication.mdx

@@ -36,7 +36,7 @@ To authenticate your API requests, you must include the API key in the `Authoriz
 
 Here's a sample API request using cURL:
 
-```
+```bash
 curl --location 'https://app.documenso.com/api/v1/documents?page=1&perPage=1' \
 --header 'Authorization: api_xxxxxxxxxxxxxxxx'
 ```