fix typo in context-providers.md

docs/docs/customize/context-providers.md

@@ -6,7 +6,7 @@ keywords: [context, "@", provider, LLM]
 
 Context Providers allow you to type '@' and see a dropdown of content that can all be fed to the LLM as context. Every context provider is a plugin, which means if you want to reference some source of information that you don't see here, you can request (or build!) a new context provider.
 
-As an example, say you are working on solving a new GitHub Issue. You type '@Isse' and select the one you are working on. Continue can now see the issue title and contents. You also know that the issue is related to the files 'readme.md' and 'helloNested.py', so you type '@readme' and '@hello' to find and select them. Now these 3 "Context Items" are displayed inline with the rest of your input.
+As an example, say you are working on solving a new GitHub Issue. You type '@Issue' and select the one you are working on. Continue can now see the issue title and contents. You also know that the issue is related to the files 'readme.md' and 'helloNested.py', so you type '@readme' and '@hello' to find and select them. Now these 3 "Context Items" are displayed inline with the rest of your input.
 
 ![Context Items](/img/context-provider-example.png)
 
@@ -200,7 +200,7 @@ For example, type "@Google python tutorial" if you want to search and discuss wa
 
 Note: You can get an API key for free at [serper.dev](https://serper.dev).
 
-### `@Isse`
+### `@Issue`
 
 Reference the conversation in a GitHub issue.
 
@@ -451,14 +451,15 @@ The HttpContextProvider makes a POST request to the url passed in the configurat
     {
       "name": "http",
       "params": {
-        "url": "https://api.example.com/v1/users",
+        "url": "https://api.example.com/v1/users"
       }
     }
   ]
 }
 ```
 
 The receiving URL should expect to receive the following parameters:
+
 ```json title="POST parameters"
 {
   query: string,
@@ -467,6 +468,7 @@ The receiving URL should expect to receive the following parameters:
 ```
 
 The response 200 OK should be a JSON object with the following structure:
+
 ```json title="Response"
 [
   {