Trying to improve readability of sentence, caused by poor english skills

Author: snakefoot

_posts/2021-08-25-nlog-5-0-preview1-ready.md

@@ -274,16 +274,17 @@ NLog LoggingProvider no longer follows the Microsoft Logger filtering configurat
 * **Reason:** It is confusing to have two seperate systems for filtering logging output. New users might
 think NLog is not working correctly after having configured NLog LoggingRules, because Microsoft LoggerFactory filters are interfering.
 
-* **Workaround:** Explicit specify `RemoveLoggerFactoryFilter = false` for NLogProviderOptions when calling `UseNLog()` to enable old behavior,
+* **Workaround:** Update NLog Logging rules to suppress the unwanted output using the new [finalMinLevel](https://github.com/NLog/NLog/wiki/Logging-Rules-FinalMinLevel)-option.
+Alternative specify `RemoveLoggerFactoryFilter = false` for NLogProviderOptions when calling `UseNLog()` to revert to old behavior,
 where Microsoft LoggerFactory filters specified in appsetting.json also applies to NLog.
 
-Alternatively the new `finalMinLevel`-option can be used to replicate the behavior of Microsoft Logging Filters:
+The new [finalMinLevel](https://github.com/NLog/NLog/wiki/Logging-Rules-FinalMinLevel)-option can be used to replicate the behavior of Microsoft Logging Filters:
 ```xml
 <rules>
     <logger name="System.*" finalMinLevel="Warn" />
     <logger name="Microsoft.*" finalMinLevel="Warn" />
     <logger name="Microsoft.Hosting.Lifetime*" finalMinLevel="Info" /> <!-- Overrides previous rule -->
-    <logger name="*" minLevel="Debug" writeTo="console" />
+    <logger name="*" minLevel="Debug" writeTo="console" /> <!-- Replace with your targets -->
 </rules>
 ```
 

_posts/2023-05-30-nlog-5-2-trim-warnings.md

@@ -3,19 +3,19 @@ layout: post
 title: NLog 5.2 without trim warnings
 ---
 
-NLog v5.2 changes the recommended way for explicit registration of NLog extensions.
-Already now the automatic scanning for assemblies containing NLog extensions was disabled with NLog v5.
-Instead NLog users are encouraged to explicitly specify what NLog extensions to load.
+NLog v5.2 is changing the recommended way for explicit registration of NLog extensions.
+NLog v5.0 stopped the automatic scanning for assemblies with NLog extensions,
+instead NLog uses was encouraged to explicitly specify what NLog extensions to load.
 
 NLog extensions are normally loaded by just specifying the assembly-name, and then NLog will dynamically
-load the assembly, and NLog will then use reflection to enumerate the types inside the assembly.
+load the assembly, and use reflection to enumerate the types inside the assembly.
 
 When using NET trimming to strip away all unreferenced code, then dynamic assembly loading will not work well.
 Dynamically loaded assemblies might reference code that have been stripped from the application. To prevent
 all these issues then NET trimming will make build warnings about such possible pitfalls. Thus previous versions
 of NLog are reported as being unsafe for NET trimming, because of the ability to dynamically load assemblies.
 
-NLog v5.2 now recommends that one registers the individual NLog extension types like this:
+NLog v5.2 now recommends to register the individual NLog extension types like this:
 ```csharp
 NLog.LogManager.Setup().SetupExtensions(ext => {
 	ext.RegisterTarget<MyCustomTarget>();

_posts/2024-10-01-nlog-6-0-goals.md

@@ -38,4 +38,4 @@ NLog should not become a blocker, when wanting to try out AOT builds.
 
 This means NLog v5 will now go into maintenance mode (together with NLog v4), and focus
 will now be on getting NLog v6 preview build ready. If having suggestions for the future direction
-of the [NLog v6 milestone](https://github.com/NLog/NLog/milestone/29) then [comments are wellcome](https://github.com/NLog/NLog/issues/4931).
+of the [NLog v6 milestone](https://github.com/NLog/NLog/milestone/29) then [comments are welcome](https://github.com/NLog/NLog/issues/4931).

index.html

@@ -29,7 +29,7 @@ <h1 class="page-header" id="features">Features</h1>
                     <h4>Easy to configure</h4>
                     <p>
                         NLog is very easy to configure, both through <a href="https://github.com/nlog/NLog/wiki/Configuration-file">configuration file</a>
-                        and <a href="https://github.com/nlog/NLog/wiki/Configuration-API">programmatically</a>.
+                        and <a href="https://github.com/NLog/NLog/wiki/Configure-from-code">programmatically</a>.
                         Even without restarting the application, the configuration can be changed.
                     </p>
                 </div>