NoAsyncRunSynchronouslyInLibrary: updated docs

To address feedback.

Author: webwarrior-ws

docs/content/how-tos/rules/FL0087.md

@@ -6,7 +6,7 @@ hide_menu: true
 
 # NoAsyncRunSynchronouslyInLibrary (FL0087)
 
-*Introduced in `0.26.7`*
+*Introduced in `0.26.8`*
 
 ## Cause
 
@@ -19,12 +19,39 @@ The rule assumes the code is in the library if none of the following is true:
 
 ## Rationale
 
-Using `Async.RunSynchronously` outside of scripts and tests can lead to program becoming non-responsive.
+Using `Async.RunSynchronously` outside of scripts, tests, and console projects can lead to program becoming non-responsive.
 
 ## How To Fix
 
 Remove `Async.RunSynchronously` and wrap the code that uses `async` computations in `async` computation, using `let!`, `use!`, `match!`, or `return!` keyword to get the result.
 
+Example:
+
+```fsharp
+let someFunc someParam =
+    let foo =
+        asyncOtherFunc someParam
+        |> Async.RunSynchronously
+    processFoo foo
+```
+
+The function can be modified to be asynchronous. In that case it might be better to prefix its name with Async:
+
+```fsharp
+let asyncSomeFunc someParam = async {
+    let! foo = asyncOtherFunc someParam
+    return processFoo foo
+}
+```
+
+In case the method/function is public, a nice C#-friendly overload that returns `Task<'T>` could be provided, suffixed with Async, that just calls the previous method with `Async.StartAsTask`:
+
+```fsharp
+let someFuncAsync someParam =
+    asyncSomeFunc someParam
+    |> Async.StartAsTask
+```
+
 ## Rule Settings
 
     {