deploy: 17f423f02c

docs/patterns/index.xml

@@ -212,7 +212,7 @@ When a new implementation is created, we need to make sure that these events are
 </span></span></span><span style="display:flex;"><span><span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#204a87;font-weight:bold">end</span><span style="color:#000;font-weight:bold">;</span><span style="color:#f8f8f8;text-decoration:underline">
 </span></span></span><span style="display:flex;"><span><span style="color:#f8f8f8;text-decoration:underline"></span>}<span style="color:#f8f8f8;text-decoration:underline">
 </span></span></span></code></pre></div><h2 id="benefits">Benefits</h2>
-<p>This new codeunit, with public events, makes the events accessible from all places, including new apps that are dependent from this app, and wants to extend the</p>
+<p>This new codeunit, with public events, makes the events accessible from all places, including new apps that are dependent from this app.</p>
 <p>The naming convention (both starting with “IScale”) also makes it very easy to find that corresponding events for the interface.</p>
 <h2 id="when-not-to-use">When not to use</h2>
 &lt;p>Obviously, the events should be carefully considered: only the events that make sense to &amp;ldquo;share&amp;rdquo; over all implementations, need this approach.&lt;/p></description></item><item><title>Docs: Façade</title><link>https://alguidelines.dev/docs/patterns/facade-pattern/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://alguidelines.dev/docs/patterns/facade-pattern/</guid><description>