Scope of this style guide and questions

Nobody has claimed this yet.

Hi,

I've been working on SystemVerilog Style Guide for my company with my colleagues.
I found your style guide and it is very well written. The goal of your stile guide and ours are very close, because we are also referring to books and papers by Stuart Sutherland, Don Mills, and Clifford Cumming as your Style Guide is.

I have some feedbacks and some proposals on your style guide.
Is your style guide only for lowRISC project?
I think your style guide can be applied to wide range of projects. If you don't mind I'd like to send pull requests to you.

Here is my fixes ready to be push.
https://github.com/lowRISC/style-guides/compare/master...hirooih:master

I have some other proposals. Some of them need Q&A with you. Some needs discussion on a separate issue ticket.
Before going to further let me know your thoughts.

Thank you sharing your great style guide.

No files, tests, or entry points are named. Read the repository's SystemVerilog style guide and the linked comparison, then clarify the guide's intended scope with maintainers before turning any agreed proposals into separate, well-defined changes.

Written by the indexing model from the issue text.