nicer bullets

docs/docs/development/module-creation.md

@@ -134,15 +134,15 @@ Once you have written and tested your module, you should prepare it for inclusio
 
 The following requirements are necessary for a module to be included in `zmk-modules`:
 
-- [] The module is named according to convention
-- [] The module has been tested and confirmed working
-- [] The module features a `README.md` file describing the module
-- [] The module is licensed under an MIT-compatible license, preferably through a `LICENSE` file
-- [] The module follows the general style of other modules of the same type found in `zmk-modules`
-- [] There are no unused files or folders present in the module
-- [] The module is up-to-date with the current version of ZMK
-- [] If the module defines keyboards or hardware components, said keyboards/components are available for public use (sold by a vendor, open source, etc.)
-- [] If the module defines boards or shields, they follow the "good board/shield definition practices"
+- [ ] The module is named according to convention
+- [ ] The module has been tested and confirmed working
+- [ ] The module features a `README.md` file describing the module
+- [ ] The module is licensed under an MIT-compatible license, preferably through a `LICENSE` file
+- [ ] The module follows the general style of other modules of the same type found in `zmk-modules`
+- [ ] There are no unused files or folders present in the module
+- [ ] The module is up-to-date with the current version of ZMK
+- [ ] If the module defines keyboards or hardware components, said keyboards/components are available for public use (sold by a vendor, open source, etc.)
+- [ ] If the module defines boards or shields, they follow the "good board/shield definition practices"
 
 ### Module File