XS ◾ 📄 Updated speak up rule to add retro sub-heading (#9886)

rules/infrastructure-healthchecks/rule.md

@@ -40,6 +40,8 @@ Adding comprehensive healthchecks is great, but if no-one is told about it - wha
 
 Depending on your needs, you may want to bake in a healthcheck UI directly into your app. Packages like [AspNetCore.HealthChecks.UI](https://www.nuget.org/packages/AspNetCore.HealthChecks.UI/) make this a breeze, and can often act as your canary in the coalmine. Cloud providers' native status/health pages can take a while to update, so having your own can be a huge timesaver.
 
+![Figure: AspNetCore.HealthChecks.UI gives you a healthcheck dashboard OOTB](https://raw.githubusercontent.com/Xabaril/AspNetCore.Diagnostics.HealthChecks/refs/heads/master/doc/images/ui-home.png)
+
 ## Handle offline infrastructure gracefully
 
 When using non-critical infrastructure like an LLM-powered chatbot, make sure to implement graceful degradation strategies. Instead of failing completely, this allows your app to respond intelligently to infrastructure outages, whether through fallback logic, informative user messages, or retry mechanisms when the service is back online.

rules/speak-up-in-meetings/rule.md

@@ -14,6 +14,7 @@ authors:
 related:
 - the-3-criteria-that-make-a-good-meeting
 - meetings-do-you-listen-more-than-you-talk
+- asking-questions
 redirects: []
 
 ---
@@ -65,6 +66,10 @@ If you're unsure about a question you want to ask, send it to a colleague via vi
 
 ## 3. **After** the meeting
 
+### Do a Retro
+
+Have a quick huddle with your colleagues and ask for feedback. They will be able to tell you the things you did great, and any areas where you might be able to improve. A retro is one of the best ways to learn and grow, so use that awesome tool.
+
 ### Practice speaking up regularly
 
 Like any skill, speaking up in meetings gets easier with practice. Start by contributing in smaller meetings or informal discussions. Over time, your confidence will grow, making it second nature to speak up in larger settings.