Fixing [!NOTE]

docs/user-manual/design-patterns/manager-worker.md

@@ -58,10 +58,10 @@ active component Manager {
     ...
 }
 ```
-> ![NOTE]
+> [!NOTE]
 > Any port types can be used to start work and signal completion as long as the worker component matches.
 
-> ![NOTE]
+> [!NOTE]
 > The manager component typically has commands, port calls, and other design elements. This above snippet just represents the interaction with the worker.
 
 **Worker Model Snippet**
@@ -75,7 +75,7 @@ active component Manager {
 }
 ```
 
-> ![NOTE]
+> [!NOTE]
 > Workers typically have no inputs (commands, ports) except those that are controlled by the manager component.
 
 The [synchronous cancel port](./common-port-patterns.md#synchronous-cancel) pattern can be applied to the manager and worker components should the worker need to support the ability to cancel ongoing work.
@@ -95,9 +95,9 @@ instance worker: ManagerWorker.Worker base id 0x1000 \
     priority 20 # Low-priority (Linux) for the Worker
 ```
 
-> ![NOTE]
+> [!NOTE]
 > Actual priorities should be determined relative to the other instances in the system. 
 
 ## Conclusion
 
-The manager/worker pattern can be used to off-load background work from a highly-responsive component to a low-priority worker. The worker then reports when the task is done thus ensuring the manager can remain responsive to requests during the duration of the work performed.g
+The manager/worker pattern can be used to off-load background work from a highly-responsive component to a low-priority worker. The worker then reports when the task is done thus ensuring the manager can remain responsive to requests during the duration of the work performed.g