Update Understanding-Bot-Powered-ACEs.md

Author: VesaJuvonen

docs/spfx/viva/bot-powered/Understanding-Bot-Powered-ACEs.md

@@ -9,7 +9,7 @@ ms.localizationpriority: high
 Bot Powered Adaptive Card Extensions (ACEs) for Microsoft Viva Connections can be used to build custom experiences for the Microsoft Viva Connections Dashboard using the Bot development model.
 
 > [!TIP]
-> You can also wathc the key areas of this article in video format on the Microsoft 365 & Power Platform Community YouTube Channel.
+> You can also watch the key areas of this article in video format on the Microsoft Community Learning YouTube Channel.
 
 > [!Video https://www.youtube.com/embed/OWPVe3n5UnM]
 
@@ -67,4 +67,4 @@ There are some architectural things that are worth being aware of to design and
 1. By default, a Bot Powered ACE **doesn't provide you with any information about the consumer tenant or user**. If you want to access information about the tenant or the user consuming your Bot Powered ACE, you have to rely on a single sign-on (SSO) enabled Bot.
 1. At the time of this writing, you **can have multiple Bots and multiple dashboard cards configured** in the **manifest.json** file of a Microsoft 365 solution. Theoretically, this configuration allows for multiple Bot Powered ACEs in a single project, if you register one Azure Bot for each. However, it's important to note that in the **manifest.json** file, only one application ID can be included in the _webApplicationInfo_ section. This section is used to configure single sign-on (SSO), which is a common requirement. So, each Visual Studio project can only have one Bot Powered ACE with SSO functionality.
 1. When rendering Quick Views in Bot Powered ACEs you can rely on the **AdaptiveCards.Templating** NuGet package and on a JSON template file defining an Adaptive Card, or you can use a code based and declarative approach. Keep into account that the **AdaptiveCards.Templating** NuGet package, at the time of this writing, can only parse and process JSON files with Adaptive Card definitions up to Adaptive Card schema v. 1.2, while using the declarative and code based model you can use any version of the Adaptive Card schema.
-1. If you have multiple instances of the same Bot Powered ACE on the same dashboard relying on single sign-on (SSO), they can **share the same security context**. In fact, users can authenticate on one of the card instances and their security context is shared across all of the instances. However, you need to manually refresh the dashboard to make all the instances aware of the authenticated context. The same happens when a user signs out from a single card instance. You need to refresh the page to make all the other card instances aware of the unauthenticated context.
+1. If you have multiple instances of the same Bot Powered ACE on the same dashboard relying on single sign-on (SSO), they can **share the same security context**. In fact, users can authenticate on one of the card instances and their security context is shared across all of the instances. However, you need to manually refresh the dashboard to make all the instances aware of the authenticated context. The same happens when a user signs out from a single card instance. You need to refresh the page to make all the other card instances aware of the unauthenticated context.