Update contribution documentation for clarity and consistency

Author: marcosqlbi

_mydocs/contribute/daxlib-libraries.md

@@ -9,7 +9,8 @@ order:          /05
 next_reading:   true
 ---
 
-**TODO**
-1) Fork one of the dev-daxlib repos based corresponding to the library name.
-2) Apply the change, commit, and submit a Pull Request.
-3) Wait for review and approval.
+**TO BE COMPLETED**
+To contribute to one of the DaxLib open-source libraries maintained by the DaxLib organization, follow these steps:
+1. Fork one of the dev-daxlib repos based corresponding to the library name.
+2. Apply the change, commit, and submit a Pull Request.
+3. Wait for review and approval.

_mydocs/contribute/fork-daxlib.md

@@ -1,7 +1,7 @@
 ---
 layout:         page
 title:          Contribute Small Libraries to DAX Lib
-menu_title:     Small libraries
+menu_title:     Small Libraries
 published:      true
 date:           2025-10-17
 modified:       2025-10-17

_mydocs/contribute/github-repo.md

@@ -1,7 +1,7 @@
 ---
 layout:         page
 title:          Contribute Medium-Large Libraries to DAX Lib
-menu_title:     Medium-Large libraries
+menu_title:     Medium-Large Libraries
 published:      true
 date:           2025-10-17
 modified:       2025-10-17

_mydocs/contribute/naming-conventions.md

@@ -1,6 +1,6 @@
 ---
 layout:         page
-title:          Naming conventions
+title:          Naming Conventions
 published:      true
 date:           2025-09-20
 modified:       2025-09-30
@@ -19,9 +19,11 @@ When creating a new package for DAX Lib, it is important to follow specific conv
      - `Contoso.Conversion` - a library of conversion functions published by Contoso.
      - `Northwind.Math.Geometry` - a library of geometrical math functions published by Northwind.
 
-2. **Package Folder Name**
+2. **Package Folder Name** (⚠️ only for Small Libraries)
 
     - The folder name for your package should be in lowercase letters and use dots to separate different levels of hierarchy.
+      > **⚠️**
+      > This naming convention must be manually managed if you create a Small Library by forking the DAX Lib repository. If you create a Medium-Large Library with a dedicated GitHub repository, the folder name will be automatically generated when the package is published to DAX Lib.
       
       Example: for a package named `Contoso.Conversion`, the folder name should be: