Fixes file name and some typos

Author: Patrick

README.md

@@ -50,7 +50,7 @@ This python package can also be used to create a serverless worker that can be d
 
 ### Quick Start
 
-Create an python script in your project that contains your model definition and the RunPod worker start code. Run this python code as your default container start command:
+Create a python script in your project that contains your model definition and the RunPod worker start code. Run this python code as your default container start command:
 
 ```python
 # my_worker.py
@@ -73,7 +73,7 @@ def is_even(job):
 runpod.serverless.start({"handler": is_even})
 ```
 
-Make sure that this file is ran when your container starts. This can be accomplished by calling it in the docker command when you setup a template at [runpod.io/console/serverless/user/templates](https://www.runpod.io/console/serverless/user/templates) or by setting it as the default command in your Dockerfile.
+Make sure that this file is ran when your container starts. This can be accomplished by calling it in the docker command when you set up a template at [runpod.io/console/serverless/user/templates](https://www.runpod.io/console/serverless/user/templates) or by setting it as the default command in your Dockerfile.
 
 See our [blog post](https://www.runpod.io/blog/serverless-create-a-basic-api) for creating a basic Serverless API, or view the [details docs](https://docs.runpod.io/serverless-ai/custom-apis) for more information.
 

docs/api/quries.md renamed to docs/api/queries.md

@@ -1,6 +1,6 @@
 # Projects
 
-A runpod project is a single folder that contains all the files needed to create and run a serverless worker.
+A RunPod project is a single folder that contains all the files needed to create and run a serverless worker.
 
 ## Convert existing worker to a project
 
@@ -10,4 +10,4 @@ You may need to update the default configuration within `runpod.toml` to match y
 
 ## Ignore Files and Folders
 
-Create a `.runpodignore` file in the root of your project to ignore files and folders from being uploaded to the runpod platform, the same file will also be used to ignore files that should not trigger a API server reload.
+Create a `.runpodignore` file in the root of your project to ignore files and folders from being uploaded to the RunPod platform, the same file will also be used to ignore files that should not trigger an API server reload.

docs/cli/references/projects.md

@@ -1,6 +1,6 @@
 # Project File
 
-Project files are stored as a `runpod.toml` file in the root of your project. This file contains all the information needed to run your project on the runpod platform.
+Project files are stored as a `runpod.toml` file in the root of your project. This file contains all the information needed to run your project on the RunPod platform.
 
 ## Example
 

docs/cli/references/runpod.toml.md

@@ -1,6 +1,6 @@
 # Getting Started
 
-The runpod python library is a powerful library providing SDK functions, API access, and CLI commands for interacting with the runpod platform.
+The RunPod python library is a powerful library providing SDK functions, API access, and CLI commands for interacting with the RunPod platform.
 
 ## Credentials File
 
@@ -12,7 +12,7 @@ api_key = "YOUR_RUNPOD_API_KEY"
 ```
 ### Profile
 
-By default all credentials are stored under the `default` profile. To switch profiles you can use the `--profile` argument on CLI commands or change the profile within a script.
+By default, all credentials are stored under the `default` profile. To switch profiles you can use the `--profile` argument on CLI commands or change the profile within a script.
 
 ```python
 import runpod

docs/getting_Started.md

@@ -2,7 +2,7 @@
 
 It is important to test your serverless workers locally before deploying them to the cloud. This will help you catch errors early and avoid wasting cloud resources. This guide will show you how to test your serverless workers locally.
 
-If any errors are returned by the worker while running a test_input job the worker will exit with a non-zero exit code. Otherwise the worker will exit with a zero exit code. This can be used to check if the worker ran successfully, for example in a CI/CD pipeline.
+If any errors are returned by the worker while running a test_input job the worker will exit with a non-zero exit code. Otherwise, the worker will exit with a zero exit code. This can be used to check if the worker ran successfully, for example in a CI/CD pipeline.
 
 ## Test Input File
 

docs/serverless/local_testing.md

@@ -24,7 +24,7 @@ The `config` parameter is a dictionary containing the following keys:
 
 ### handler
 
-The handler function can either had a standard return or be a generator function. If the handler is a generator function, it will be called with the job input and the generator will be iterated over until it is exhausted.
+The handler function can either have a standard return or be a generator function. If the handler is a generator function, it will be called with the job input and the generator will be iterated over until it is exhausted.
 
 ## Worker Refresh