diff --git a/docs/quickstart-continue.mdx b/docs/quickstart-continue.mdx index edb4058..9a065ea 100644 --- a/docs/quickstart-continue.mdx +++ b/docs/quickstart-continue.mdx @@ -174,9 +174,9 @@ keys or passwords. You've certainly taken steps to avoid checking these into your source repo, but they are fair game for LLMs to use as context and training. -Open the `conf.ini` or `app.json` file from the demo repo in the VS Code editor -and examine the contents. In the Continue chat input, type `@Files` and select -the file to include it as context, and ask Continue to explain the file. +Open the `conf.ini` or `eth/app.json` file from the demo repo in the VS Code +editor and examine the contents. In the Continue chat input, type `@Files` and +select the file to include it as context, and ask Continue to explain the file. For example, using `conf.ini`: @@ -204,13 +204,13 @@ Learn more in [Secrets encryption](./features/secrets-encryption.md). ### Assess dependency risk -Open the `packages.py` file from the demo repo in the VS Code editor and examine -the import statements at the top. As with the previous step, type `@Files`, this -time selecting the `packages.py` file to add it to your prompt. Then ask -Continue to analyze the file. +Open the `python/app.py` file from the demo repo in the VS Code editor and +examine the import statements at the top. As with the previous step, type +`@Files`, this time selecting the `python/app.py` file to add it to your prompt. +Then ask Continue to analyze the file. ```plain title="Continue chat" -@packages.py Please analyze this file +@app.py Please analyze this file ``` Using its up-to-date knowledge from diff --git a/docs/quickstart-copilot.mdx b/docs/quickstart-copilot.mdx index fdedba4..3e20fc9 100644 --- a/docs/quickstart-copilot.mdx +++ b/docs/quickstart-copilot.mdx @@ -129,9 +129,9 @@ keys or passwords. You've certainly taken steps to avoid checking these into your source repo, but they are fair game for Copilot to send to its language models as context. -Open the `conf.ini` or `app.json` file from the demo repo in the VS Code editor. -In the Copilot chat panel, observe that Copilot has automatically loaded the -active file as context. +Open the `conf.ini` or `eth/app.json` file from the demo repo in the VS Code +editor. In the Copilot chat panel, observe that Copilot has automatically loaded +the active file as context.