@@ -8,9 +8,9 @@ easy and transparent as possible, whether it's:
88- Submitting a fix
99- Proposing new features
1010
11- ## We develop with Github
11+ ## We develop with GitHub
1212
13- We use github to host code, to track issues and feature requests, as well as accept pull requests.
13+ We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
1414
1515## Finding tasks to work on
1616
@@ -39,7 +39,7 @@ to share any relevant context and increase its chances of getting merged.
3939
4040Note: make sure to follow the [ Conventional Commits] ( https://www.conventionalcommits.org/en/v1.0.0/ ) guidelines when creating a PR.
4141
42- ## Report bugs using Github 's [ issues] ( https://github.com/tobymao/sqlglot/issues )
42+ ## Report bugs using GitHub 's [ issues] ( https://github.com/tobymao/sqlglot/issues )
4343
4444We use GitHub issues to track public bugs. Report a bug by opening a new issue.
4545
@@ -54,7 +54,7 @@ We use GitHub issues to track public bugs. Report a bug by opening a new issue.
5454- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
5555- References (e.g. documentation pages related to the issue)
5656
57- ## Start a discussion using Github 's [ discussions] ( https://github.com/tobymao/sqlglot/discussions )
57+ ## Start a discussion using GitHub 's [ discussions] ( https://github.com/tobymao/sqlglot/discussions )
5858
5959[ We use GitHub discussions] ( https://github.com/tobymao/sqlglot/discussions/190 ) to discuss about the current state
6060of the code. If you want to propose a new feature, this is the right place to do it. Just start a discussion, and
0 commit comments