fixup! move traits docs to the docs

Author: kukushechkin

Sources/Logging/Docs.docc/DisableLogLevelsDuringCompilation.md

@@ -1,17 +1,17 @@
-### Disable log levels during compilation
+# Disable log levels during compilation
 
 SwiftLog provides compile-time traits to eliminate less severe log levels from
 your binary reducing the runtime overhead.
 
-#### Motivation
+## Motivation
 
 When deploying applications to production, you often know in advance which log
 levels will never be needed. For example, a production service might only need
 warning and above, while trace and debug levels are only useful during
 development. By using traits, you can completely remove these unnecessary log
 levels at compile time, achieving zero runtime overhead.
 
-#### Available traits
+## Available traits
 
 SwiftLog defines seven maximum log level traits, ordered from most permissive
 to most restrictive:
@@ -33,12 +33,13 @@ By default (when no traits are specified), all log levels are available.
 When you specify a maximum log level trait, all less severe levels are
 completely removed from your binary at compile time. This applies to both
 level-specific methods (e.g., `logger.debug()`) and calls to the generic
-`logger.log(level:)` method.
+`logger.log(level:)` method. Traits are additive. If multiple max level traits
+are specified, the most restrictive one takes effect.
 
-> Note: Traits are additive. If multiple max level traits are specified, the
-> most restrictive one takes effect.
+> Note: Traits should only be set by the applications and not libraries as
+> any traits defined in a transitive dependency will affect the whole resolution tree.
 
-#### Example
+## Example
 
 To enable a trait, specify it when declaring your package dependency:
 

Sources/Logging/Docs.docc/index.md

@@ -92,6 +92,7 @@ backend.
 
 - <doc:LoggingBestPractices>
 - <doc:ImplementingALogHandler>
+- <doc:DisableLogLevelsDuringCompilation>
 
 ### Contributing