docs: fixed lint errors

Author: Prasad Bhat

README.md

@@ -38,7 +38,6 @@ Welcome to the official docs for [**CodeRabbit**](https://coderabbit.ai), the co
 ## Getting Started
 
 1. Make sure that you have the following prerequisites installed:
-
    - [Node.js](https://nodejs.org/)
    - [pnpm](https://pnpm.io/installation)
 

docs/getting-started/configure-coderabbit.md

@@ -50,7 +50,7 @@ import YamlEditor from '@site/src/components/YamlEditor/YamlEditor';
   </div>
 </div>
 
-The configuration file can be used to set various options. 
+The configuration file can be used to set various options.
 
 ```mdx-code-block
 import SchemaViewer from '@site/src/components/SchemaViewer';

docs/getting-started/quickstart.md

@@ -5,7 +5,6 @@ description: See CodeRabbit in action, using a live GitHub repository.
 sidebar_position: 1
 ---
 
-
 # Quickstart
 
 This tutorial gives you a hands-on demonstration of CodeRabbit, using a real, GitHub-based repository. It guides you through the following tasks:
@@ -130,8 +129,7 @@ After a few moments, CodeRabbit posts its reply, explaining its motivations for
   <p>If you prefer to skip docstrings for obvious utility functions in this project, that's perfectly reasonable. Would you like me to adjust my review approach regarding documentation for this repository?</p>
 </div>
 
-In this case, CodeRabbit is offering to adjust its future behavior when reviewing changes to this repository. Instead, follow the next step to ask CodeRabbit to implement part of its suggestions.
-2. Post the following as another new comment:
+In this case, CodeRabbit is offering to adjust its future behavior when reviewing changes to this repository. Instead, follow the next step to ask CodeRabbit to implement part of its suggestions. 2. Post the following as another new comment:
 
 <div class="custom-chat-bubble">
   <div class="chat-content">@coderabbitai generate docstrings</div>

docs/guides/custom-reports.md

@@ -327,17 +327,14 @@ Generate a weekly code review report for the author of this pull request only fo
 **Scoring Parameters:**
 
 1. **Basic Code Standards (Score out of 2)**
-
    - Avoidance of hard-coded values
    - No repetition of code (DRY principle)
 
 2. **Code Readability (Score out of 2)**
-
    - Presence of meaningful comments
    - Proper variable declaration using `const` and `let`
 
 3. **Error Handling (Score out of 4)**
-
    - Handling failure scenarios (e.g., try-catch, fallbacks)
    - Proper loading state implementation (e.g., button click loading states)
    - Handling edge cases (e.g., checking for undefined or missing values)
@@ -466,25 +463,21 @@ You will create a new chart averaging all the values from various pull requests
 ## Best Practices
 
 1. **Be Specific**
-
    - Clearly define what should be included/excluded
    - Use precise language to avoid ambiguity
    - Specify exact metrics you want to track
 
 2. **Structure Matters**
-
    - Start with high-level summaries
    - Use consistent grouping patterns
    - Include clear section breaks
 
 3. **Keep it Relevant**
-
    - Focus on actionable information
    - Avoid redundant data points
    - Consider your audience's needs
 
 4. **Optimize Readability**
-
    - Use appropriate formatting
    - Include visual breaks
    - Maintain consistent styling

docs/guides/install-vscode.md

@@ -31,7 +31,6 @@ To install the CodeRabbit extension, follow these steps:
 1. Click **Install**.
 
 1. A **Log in to CodeRabbit to get started** dialog appears. Click **Login**. If the dialog gets dismissed or times out first, then you can follow these alternate steps:
-
    1. Click the CodeRabbit icon in the VSCode activity bar.
 
    1. Click the **Use CodeRabbit for Free** button.
@@ -41,7 +40,6 @@ To install the CodeRabbit extension, follow these steps:
 1. In your web browser, log into your CodeRabbit account.
 
 1. After signing in, the browser will redirect you back to VSCode. If the redirect does not occur, follow these steps:
-
    1. Copy the code displayed in the success window.
 
    2. Click **Paste code from browser**.

docs/guides/issue-chat.md

@@ -123,19 +123,16 @@ Example:
 ## Best Practices
 
 1. **Be Specific**
-
    - Provide context in your questions
    - Mention specific files or features when relevant
    - Clarify your goals or requirements
 
 2. **Iterative Refinement**
-
    - Start with broad questions
    - Follow up for more details
    - Ask for clarification when needed
 
 3. **Collaborative Planning**
-
    - Include stakeholders in the conversation
    - Use issue chat to document decisions
    - Reference related issues or PRs

docs/guides/linked-issues.md

@@ -42,7 +42,6 @@ Create descriptive, technical titles that clearly state the goal:
 Write comprehensive descriptions that provide clear technical context:
 
 1. **Problem Statement**
-
    - Clearly describe what needs to be changed
    - Include technical details about affected components
    - Reference specific files or functions if known
@@ -144,19 +143,16 @@ Only the issue title and description are considered in the assessment. Comments
 ## Tips for Better Assessments
 
 1. **Be Specific**
-
    - Include clear, measurable objectives
    - List specific technical requirements
    - Reference affected code components
 
 2. **Provide Context**
-
    - Explain why changes are needed
    - Document current behavior
    - Describe expected outcomes
 
 3. **Use Technical Details**
-
    - Include file paths when known
    - Reference specific functions or classes
    - Mention relevant technologies

docs/guides/reports-overview.md

@@ -18,7 +18,6 @@ You can track and analyze pull request activity across your organization's repos
 There are two ways to generate reports:
 
 - **[Scheduled Reports](/guides/scheduled-reports)**: Set up automated, recurring reports that are delivered to your team on a set schedule. **Use this option if you want to adjust your settings and send a report more than once**. Supported delivery channels include the following:
-
   - Email
   - Discord
   - Slack

docs/guides/roles.md

@@ -127,18 +127,18 @@ This sends an email to the address that you specified. After the recipient compl
 The following table lists the CodeRabbit administrative functionality
 available to each of the CodeRabbit roles.
 
-| Resource | Admin | Member | Billing Admin |
-|----------|-------|---------|---------------|
-| Learning Resources | Read/Write | Read-only | No access |
-| Metrics/Dashboard | Read/Write | No access | No access |
-| Reports | Read/Write | Read-only | No access |
-| Integrations | Read/Write | Read-only | No access |
-| Repository Settings | Read/Write | Read-only | No access |
-| Organization Settings | Read/Write | Read-only | No access |
-| User Management | Read/Write | Read-only | Read-only |
-| Subscription Management | Read/Write | Read-only | Read/Write |
-| Billing Management | Read/Write | No access | Read/Write |
+| Resource                | Admin      | Member    | Billing Admin |
+| ----------------------- | ---------- | --------- | ------------- |
+| Learning Resources      | Read/Write | Read-only | No access     |
+| Metrics/Dashboard       | Read/Write | No access | No access     |
+| Reports                 | Read/Write | Read-only | No access     |
+| Integrations            | Read/Write | Read-only | No access     |
+| Repository Settings     | Read/Write | Read-only | No access     |
+| Organization Settings   | Read/Write | Read-only | No access     |
+| User Management         | Read/Write | Read-only | Read-only     |
+| Subscription Management | Read/Write | Read-only | Read/Write    |
+| Billing Management      | Read/Write | No access | Read/Write    |
 
 ## What's next {#whats-next}
 
-- [Manage your subscription](/getting-started/subscription-management)
+- [Manage your subscription](/getting-started/subscription-management)

docs/guides/scheduled-reports.md

@@ -28,7 +28,6 @@ The schedule configuration allows you to set precise timing for your reports:
 #### Frequency Options
 
 - **Days of Week**
-
   - Select any combination of days (Sun-Sat)
   - Set frequency (every 1-3 weeks)
   - Ideal for weekly team syncs or sprint reviews
@@ -232,12 +231,10 @@ Deleting a report will immediately stop all scheduled runs and remove access to
 ## Best Practices
 
 1. **Scheduling**
-
    - Align report timing with your team's workflow
    - Consider timezone differences for distributed teams
 
 2. **Content**
-
    - Keep prompts focused on actionable information
    - Use grouping to improve readability
    - Exclude unnecessary details that may create noise