diff options
author | Nate Sesti <33237525+sestinj@users.noreply.github.com> | 2023-07-27 16:59:49 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-07-27 16:59:49 -0700 |
commit | 823ab0a8c65a5e116e43afe61e7a720151e59111 (patch) | |
tree | 837146ff996191283e85a61ee7c5f88c8385f222 /docs | |
parent | 184685178b7a120b100f504f7ff779d05e43ff71 (diff) | |
download | sncontinue-823ab0a8c65a5e116e43afe61e7a720151e59111.tar.gz sncontinue-823ab0a8c65a5e116e43afe61e7a720151e59111.tar.bz2 sncontinue-823ab0a8c65a5e116e43afe61e7a720151e59111.zip |
Update how-to-use-continue.md
Diffstat (limited to 'docs')
-rw-r--r-- | docs/docs/how-to-use-continue.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/docs/how-to-use-continue.md b/docs/docs/how-to-use-continue.md index 7411c45f..235a87b7 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 any code that you don’t understand and type `tell me how this code works` +1. Highlight any code that you don’t understand and type `tell me how this code works` in the text box of the Continue side bar 2. If the explanation seems reasonable, then, while still highlighting the code, type `how would you change this code to [INSERT TASK]?` 3. If this explanation is also pretty good, then, while still highlighting the code, 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 |