Fixes after review round

Author: jansenbe

docs/spfx/viva/bot-powered/images/Bot-Powered-ACEs-Market-Place-ValidManifest.png

@@ -30,10 +30,13 @@ Market place acceptance criteria overview:
 
 ## Making your Bot Powered ACEs available in Viva Connections
 
-Bot Powered ACEs that are added as part of a Teams application in market place will become automatically available as cards for adding to the Viva Connections dashboard, there's **no explicit install required** of the Teams application containing the Bot Powered ACEs. So, by default, once your Teams application containing Bot Powered ACEs is published in the market place all Viva Connection dashboard admins for all tenants will see your ACEs appearing in the card picker when they configure their Viva Connection dashboards. The Teams admin can however control ACE visibility as explained in next chapter.
+Bot Powered ACEs that are added as part of a Teams application in market place will become automatically available as cards for adding to the Viva Connections dashboard, there's **no explicit install required** of the Teams application containing the Bot Powered ACEs. So, by default, once your Teams application containing Bot Powered ACEs is published in the market place all Viva Connection dashboard admins for all tenants will see your ACEs appearing in the card picker when they configure their Viva Connection dashboards. The Teams admin can however control ACE visibility via policies controlling app availability in Teams, this will be explained in next chapter.
 
 ## Bot Powered ACEs governance
 
-Bot Powered ACEs will become automatically available as mentioned earlier, but the Teams admin does have an option to control visibility. ACEs will only show up if their Teams application has not been blocked by the Teams admin, so [allowing or blocking applications](https://learn.microsoft.com/microsoftteams/manage-apps#allow-or-block-apps) is the approach that Teams admins can use to govern ACE visibility. When a Teams application gets blocked and ACEs where not yet used then they'll now show up in the card picker anymore and cannot be added to the dashboard. If the ACEs were already added to a Viva Connections dashboard then at runtime the respective cards simply will not show up, at design time an "error card" will be showing indicating that the card might have been removed/blocked by the Teams administrator.
+Bot Powered ACEs will become automatically available as mentioned earlier, but the Teams admin does have an option to control visibility. ACEs will only show up if their Teams application has not been blocked by the Teams admin, so [allowing or blocking applications](https://learn.microsoft.com/microsoftteams/manage-apps#allow-or-block-apps) is the approach that Teams admins can use to govern ACE visibility. When a Teams application gets blocked and ACEs were not yet used then they'll not show up in the card picker anymore and cannot be added to the dashboard. If the ACEs were already added to a Viva Connections dashboard then at runtime the respective cards simply will not show up, at design time an "error card" will be showing indicating that the card might have been removed/blocked by the Teams administrator.
+
+> [!Note]
+> Blocking and unblocking a Teams app will not immediately see effect on the Viva Connections dashboards using the cards, it can take several hours before the impact is visible.
 
 ![An Adaptive Card Extension showing that the card was blocked by the Teams admin.](./images/Bot-Powered-ACEs-Market-Place-Block.png)