Small fixes

Author: rachfop

.github/ISSUE_TEMPLATE/bug-report.md

@@ -12,6 +12,7 @@ A clear and concise description of what the bug is.
 
 **To Reproduce**
 Steps to locate the bug:
+
 1. Go to '...'
 2. Click on '...'
 3. Scroll down to '...'
@@ -24,18 +25,22 @@ A clear and concise description of what you expected to find.
 If applicable, add screenshots to help explain your problem.
 
 ## If describing a mismatch with a RunPod product, please include the following information about your environment:
+
 **Desktop:**
- - OS: [e.g. iOS]
- - Browser [e.g. chrome, safari]
- - Version [e.g. 22]
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
 
 **Smartphone:**
- - Device: [e.g. iPhone6]
- - OS: [e.g. iOS8.1]
- - Browser [e.g. stock browser, safari]
- - Version [e.g. 22]
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
 
 **Interface:**
+
 - Web interface, CLI, or web terminal?
 
 **

docs/pods/overview.md

@@ -4,7 +4,7 @@ description: Learn about Pods.
 sidebar_position: 1
 ---
 
-Pods are running container instances. You can pull an instance from a container registry such as Docker Hub, GitHub Container Registry, Amazon Elastic Container Registry, or another compatible registry. 
+Pods are running container instances. You can pull an instance from a container registry such as Docker Hub, GitHub Container Registry, Amazon Elastic Container Registry, or another compatible registry.
 
 :::note
 

docs/pods/savings-plans.md

@@ -10,9 +10,10 @@ Savings Plans are a powerful cost-saving feature designed to optimize your RunPo
 
 To start saving with RunPod's Savings Plans, ensure you have sufficient RunPod credits in your account.
 
-There are two ways to create a savings plan. 
-- Add a Savings Plan to your existing Pod from the Pod dashboard. 
-- Initiate a Savings Plan during Pod deployment. 
+There are two ways to create a savings plan.
+
+- Add a Savings Plan to your existing Pod from the Pod dashboard.
+- Initiate a Savings Plan during Pod deployment.
 
 Regularly check the **Savings Plans** section to track your Savings Plans and associated pods.
 
@@ -23,7 +24,7 @@ Regularly check the **Savings Plans** section to track your Savings Plans and as
 
 **Reduced Costs**: By paying upfront for a Savings Plan, you can enjoy discounted rates on uninterrupted instances. This means significant cost savings for your RunPod deployments.
 
-**Flexible Savings**: When you stop a Pod, the Savings Plan associated with it applies to your next deployment of the same card. This means you continue to benefit from your savings commitment even after temporary pauses in your pod usage. 
+**Flexible Savings**: When you stop a Pod, the Savings Plan associated with it applies to your next deployment of the same card. This means you continue to benefit from your savings commitment even after temporary pauses in your pod usage.
 
 :::warning
 

docs/pods/storage/_volume.md

@@ -6,4 +6,4 @@ Volumes can be:
 
 ## Persistent
 
-## Ephemeral
+## Ephemeral

docs/pods/templates/manage-templates.md

@@ -39,5 +39,4 @@ Use environment variables to pass configuration settings and secrets to your con
 
 ![](/img/docs/b7670dd-image.png)
 
-
 RunPod also provides a set of predefined [environment variables](/pods/references/environment-variables) that provide information about the pod, such as the unique identifier for your pod (`RUNPOD_POD_ID`), the API key used to make RunPod API calls to the specific pod (`RUNPOD_API_KEY`), the name of the host server the pod is running on (`RUNPOD_POD_HOSTNAME`), and more.

docs/serverless/endpoints/overview.md

@@ -15,5 +15,3 @@ You can use both asynchronous and synchronous jobs.
 Ensure you have a RunPod API key, available under user settings, for identification and billing purposes. Remember, your inputs or outputs are not retained beyond 30 minutes to ensure privacy.
 
 :::
-
-

docs/serverless/references/operations.md

@@ -4,9 +4,9 @@ description: "Comprehensive guide on interacting with models using RunPod's API
 sidebar_position: 2
 ---
 
-RunPod's endpoints facilitate submitting jobs and retrieving outputs. 
+RunPod's endpoints facilitate submitting jobs and retrieving outputs.
 
-To use these endpoints, you will need to have your endpoint ID. 
+To use these endpoints, you will need to have your endpoint ID.
 The constructed URL will start with `https://api.runpod.ai/v2/{endpoint_id}/{operation}` followed by an operation.
 
 Operations available to all users are:

docs/serverless/workers/handlers/overview.md

@@ -74,4 +74,3 @@ This can be used to check if the worker ran successfully, for example, in a CI/C
 
 - For information on testing your handler locally, see [Local testing](/serverless/workers/development/local-testing).
 - For information on setting a continuous integration pipeline, see [Continuous integration](/serverless/workers/deploy).
-

docs/tutorials/serverless/run-your-first.md

@@ -63,7 +63,6 @@ If your job is still processing, the response will indicate that. Here's an exam
 }
 ```
 
-
 ### Get Completed Job Status
 
 Once your job is complete, you'll receive a final response like this:

docusaurus.config.js

@@ -80,7 +80,7 @@ const config = {
 
   themeConfig: {
     colorMode: {
-      defaultMode: 'dark',
+      defaultMode: "dark",
     },
     // algolia: {
     //  appId: "LZTDWL431O",
@@ -213,7 +213,7 @@ const config = {
       defer: true,
     },
   ],
-  plugins: [require.resolve('docusaurus-lunr-search')],
+  plugins: [require.resolve("docusaurus-lunr-search")],
 };
 
 export default config;