summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorLangLangBart <92653266+LangLangBart@users.noreply.github.com>2023-09-15 18:37:09 +0200
committerGitHub <noreply@github.com>2023-09-15 09:37:09 -0700
commit775d051b4bcdbe07fbd38fae4d3e36e79234eb56 (patch)
treec8d3c26ac42ef9a1ca5cab601f43488675375161 /docs
parentffc242ef2ab4ef16306afb237a781937a6c6d52c (diff)
downloadsncontinue-775d051b4bcdbe07fbd38fae4d3e36e79234eb56.tar.gz
sncontinue-775d051b4bcdbe07fbd38fae4d3e36e79234eb56.tar.bz2
sncontinue-775d051b4bcdbe07fbd38fae4d3e36e79234eb56.zip
fix: some typos (#478)
Diffstat (limited to 'docs')
-rw-r--r--docs/docs/how-to-use-continue.md2
-rw-r--r--docs/docs/walkthroughs/create-a-recipe.md2
-rw-r--r--docs/docs/walkthroughs/use-the-gui.md4
3 files changed, 4 insertions, 4 deletions
diff --git a/docs/docs/how-to-use-continue.md b/docs/docs/how-to-use-continue.md
index bf61a033..3f21d92c 100644
--- a/docs/docs/how-to-use-continue.md
+++ b/docs/docs/how-to-use-continue.md
@@ -12,7 +12,7 @@ As you use Continue more, you will learn when to trust it. A great way to get st
If you are trying to use it for a new task and don’t have a sense of how much Continue can help you complete it, it can often be helpful to start like this:
-1. Highlight the code section(s) that you don’t understand and type "tell me how this code works" in the intput box
+1. Highlight the code section(s) that you don’t understand and type "tell me how this code works" in the input box
2. If the explanation seems reasonable, then, while still highlighting the code section(s), type "how would you change this code to [INSERT TASK]?"
3. If this explanation is also pretty good, then, while still highlighting the code section(s), type `/edit [INSERT TASK]`
4. If it does not work on first attempt, click `reject` on its suggestions and try again—often it will make a different suggestion each time
diff --git a/docs/docs/walkthroughs/create-a-recipe.md b/docs/docs/walkthroughs/create-a-recipe.md
index 2cb28f77..3ec641c6 100644
--- a/docs/docs/walkthroughs/create-a-recipe.md
+++ b/docs/docs/walkthroughs/create-a-recipe.md
@@ -54,7 +54,7 @@ class CreatePipelineRecipe(Step):
### Using the SDK
-You will want to use the SDK when you are opening directories, editing files, using models, etc. This will ensure that these actions are recorded as steps, so they are reviewable, reversable, and rerunnable.
+You will want to use the SDK when you are opening directories, editing files, using models, etc. This will ensure that these actions are recorded as steps, so they are reviewable, reversible, and rerunnable.
### Allow for configurability
diff --git a/docs/docs/walkthroughs/use-the-gui.md b/docs/docs/walkthroughs/use-the-gui.md
index 055150c7..33bc3b62 100644
--- a/docs/docs/walkthroughs/use-the-gui.md
+++ b/docs/docs/walkthroughs/use-the-gui.md
@@ -8,7 +8,7 @@
3. Press the `Continue` button
-4. Review the explaination of what was edited and why on the Continue GUI
+4. Review the explanation of what was edited and why on the Continue GUI
5. Check the code that was edited by the LLM in the code editor
@@ -22,7 +22,7 @@ Context is not carried across steps at the moment, so you will need to repeat an
## Review actions taken
-Whether you are using a recipe or not, you will want to review the explainations of what the LLM did and check the code that it generated. You are ultimately responsible for any code that you ship, even if it was written by a LLM.
+Whether you are using a recipe or not, you will want to review the explanations of what the LLM did and check the code that it generated. You are ultimately responsible for any code that you ship, even if it was written by a LLM.
## Reverse button