Skip to content

Commit 3b8aa32

Browse files
author
Jun
authored
Update README.md
Fixed some potential misspellings/errors.
1 parent e3d3e7d commit 3b8aa32

File tree

1 file changed

+5
-5
lines changed
  • 10-Challenging-GitHub-Copilot-with-SQL

1 file changed

+5
-5
lines changed

10-Challenging-GitHub-Copilot-with-SQL/README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ In this workshop, you will:
2626
- Use advanced GitHub Copilot interaction techniques to deal with complex problems regarding SQL queries.
2727
- Iterate, validate, and refine answers to get better and more accurate suggestions
2828
- Apply generic concepts that can improve suggestions and select from different strategies that can yield better results.
29-
- Get a clear understanding on poor prompting techniques, and how these can
29+
- Get a clear understanding of poor prompting techniques, and how these can
3030
affect drastically the output from GitHub Copilot.
3131

3232
## :mega: Prerequisites
@@ -102,7 +102,7 @@ In SQL, this could involve ensuring that empty datasets, null values, or unexpec
102102
> Thinking through edge cases helps you build more resilient, generalized solutions.
103103
104104
### 8. Use Tools Effectively
105-
Whether you’re using GitHub Copilot, a query builder, or another form of automation, leverage the tools at your disposal but make sure you're guiding them with the right context. Tools are great for speeding up the generation, but they still need well-structured inputs and validation from you.
105+
Whether you’re using GitHub Copilot, a query builder, or another form of automation, leverage the tools at your disposal, but make sure you're guiding them with the right context. Tools are great for speeding up the generation, but they still need well-structured inputs and validation from you.
106106

107107
For Copilot, ensure that your prompts are detailed, but concise. Tools often work best when given structured input that leaves little ambiguity.
108108

@@ -146,7 +146,7 @@ Although not required, some of the features this workshop covers are in these Mi
146146

147147
## Contributing
148148

149-
This project welcomes contributions and suggestions. Most contributions require you to agree to a
149+
This project welcomes contributions and suggestions. Most contributions require you to agree to a
150150
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
151151
the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
152152

@@ -155,7 +155,7 @@ a CLA and decorate the PR appropriately (e.g., status check, comment). Simply fo
155155
provided by the bot. You will only need to do this once across all repos using our CLA.
156156

157157
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
158-
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
158+
For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
159159
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
160160

161161
## Trademarks
@@ -164,4 +164,4 @@ This project may contain trademarks or logos for projects, products, or services
164164
trademarks or logos is subject to and must follow
165165
[Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general).
166166
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
167-
Any use of third-party trademarks or logos are subject to those third-party's policies.
167+
Any use of third-party trademarks or logos is subject to those third-parties' policies.

0 commit comments

Comments
 (0)