Update 2-how-we-style-our-sql.md

[Vhonani-Nelwamondo]

Group by column names

What are you changing in this pull request and why?

Checklist

• I have reviewed the Content style guide so my content adheres to these guidelines.
• The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
• I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
• The content in this PR requires a dbt release note, so I added one to the release notes page.

[welcome]

Hello!👋 Thanks for contributing to the dbt product documentation and opening this pull request! ✨
We use Markdown and some HTML to write the dbt product documentation. When writing content, you can use our style guide and content types to understand our writing standards and how we organize information in the dbt product docs.
We'll review your contribution and respond as soon as we can. 😄

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	Dec 10, 2024 10:07am

[vercel]

@Vhonani-Nelwamondo is attempting to deploy a commit to the dbt-labs Team on Vercel.

A member of the Team first needs to authorize it.

[mirnawong1]

hey @Vhonani-Nelwamondo , thanks for opening this pr up and great initiative!

grouping by is definitely a matter of preference and our best practice stance is to group by number, not column name. we explain our reasons in our article here.

since this change doesn’t align with our best practices, i’ll go ahead and close this PR. however, we really appreciate your effort, and we’d love to see more contributions from you in the future. if you have other ideas or edits in mind, feel free to submit them — we’re always excited to collaborate!

thanks again for your contribution! 🙌