docs: STYLE GUIDE attribute ordering convention

Author: BhoomishGupta

STYLE_GUIDE.md

@@ -61,16 +61,15 @@ focus on the semantics of the proposed changes rather than style and formatting.
   ```  
   When defining many arrays of the same dimension, `dimension` can be used as an exception if it makes the code less verbose.
 * If the `optional` attribute is used to declare a dummy argument, it should follow the `intent` attribute.
-* For module procedures, declare attributes before the `module` keyword for better retro compatibility:
-  Use this:  
-  ```
-  <attribute> <attribute> module <function/subroutine> <name>
-  ```  
-  instead of:  
-  ```
-  module <attribute> <attribute> <function/subroutine> <name>
-  ```
-
+* For module procedures, it is recommended to declare attributes before the module keyword for better retro compatibility (Projects using CMake versions lower than CMake 3.25.0 are concerned see Spurious modules).
+Prefere the following pattern:
+```
+<attribute> <attribute> module <function/subroutine> <name>
+```
+instead of:
+```
+module <attribute> <attribute> <function/subroutine> <name>
+```
 ## End <scope> block closing statements
 
 Fortran allows certain block constructs or scopes to include the name of the program unit in the end statement.