@@ -217,23 +217,23 @@ that aren't satisfied due to the requirements on the `Echo` type itself. For
217217a seasoned *Merq* developer, this is a no-brainer, but for new developers,
218218it can be a bit puzzling:
219219
220- 
220+ 
221221
222222A code fix is provided to automatically implement the required interfaces
223223in this case:
224224
225- 
225+ 
226226
227227Likewise, if a consumer attempted to invoke the above `Echo` command asynchronously
228228(known as the [async over sync anti -pattern ](https:// devblogs.microsoft.com/pfxteam/should-i-expose-asynchronous-wrappers-for-synchronous-methods/)),
229229 they would get a somewhat unintuitive compiler error:
230230
231- 
231+ 
232232
233233But the second error is more helpful , since it points to the actual problem ,
234234and a code fix can be applied to resolve it :
235235
236- 
236+ 
237237
238238The same analyzers and code fixes are provided for the opposite anti -pattern ,
239239known as [sync over async ](https :// devblogs.microsoft.com/pfxteam/should-i-expose-synchronous-wrappers-for-asynchronous-methods/),
@@ -341,7 +341,7 @@ dotnet counters monitor --process-id [PROCESS_ID] --counters Merq
341341
342342Example rendering from the included sample console app :
343343
344- ! [dotnet - counters screenshot ](https :// github. com/devlooped/Merq/blob/ main/assets/img/dotnet-counters.png?raw=true )
344+ ! [dotnet - counters screenshot ](https :// raw.githubusercontent. com/devlooped/Merq/main/assets/img/dotnet-counters.png)
345345
346346## Duck Typing Support
347347
0 commit comments