Merge pull request #184 from redpanda-data/michele/lowercase-transcripts-in-prose

docs: lowercase transcripts when it is not the tab name

Author: micheleRP

modules/connect/pages/create-agent.adoc

@@ -201,7 +201,7 @@ For more about agent cards and how they're consumed, see xref:connect:a2a-concep
 Two tabs on the agent detail page support testing and observability:
 
 * *Inspector*: Send test prompts interactively and inspect each step of the agent's reasoning, tool calls, and responses. Use Inspector during development and tuning. The composer shows the agent's provider and model as read-only, so a test run always uses the agent's saved configuration.
-* *Transcripts*: Records every conversation against the agent (prompt, tool calls, tool outputs, final response). Use Transcripts to audit production behavior.
+* *Transcripts*: Records every conversation against the agent (prompt, tool calls, tool outputs, final response). Use transcripts to audit production behavior.
 
 To test the agent in Inspector:
 

modules/monitor/pages/transcripts.adoc

@@ -157,7 +157,7 @@ For long-running conversations, accept some reconstruction; for short conversati
 
 * Confirm the agent or MCP server actually ran: Check its logs and the corresponding session or task topic.
 * Confirm your user can read transcripts. Outside the Admin role, transcript reads come from an xref:control:access-policies.adoc[access policy] naming the `Transcript` actions. Check the Access page for a policy that covers your user or one of its groups, and for a `forbid` that overrides it. See xref:control:permissions-reference.adoc#transcript-permissions[Transcript permissions].
-* Confirm the feature flag enabling Transcripts is on for your environment.
+* Confirm the feature flag enabling transcripts is on for your environment.
 
 == Next steps
 

modules/monitor/pages/troubleshoot-ai-agents.adoc

@@ -176,15 +176,15 @@ Critical rules:
 
 * Include "never fabricate" rules in all system prompts
 * Test with requests that require unavailable data
-* Monitor *Transcripts* and session topic for fabricated responses
+* Monitor transcripts and session topic for fabricated responses
 
 === Analyzing conversation patterns
 
 **Symptoms:** Agent behavior is inconsistent or produces unexpected results.
 
 **Solution:**
 
-Review conversation history in *Transcripts* to identify problematic patterns:
+Review conversation history in transcripts to identify problematic patterns:
 
 * Agents calling the same tool repeatedly: Indicates loop detection is needed
 * Large gaps between messages: Suggests tool timeout or slow execution
@@ -246,7 +246,7 @@ Diagnose and fix issues related to agent speed and resource consumption.
 
 **Solution:**
 
-. Review token usage in *Transcripts*.
+. Review token usage in transcripts.
 . Lower max iterations for this agent.
 . Optimize tool responses to return less data:
 +