chore(docs): remove remaining yml references from docs (#1492)

Author: waleedlatif1

apps/docs/content/docs/en/blocks/agent.mdx

@@ -175,33 +175,7 @@ Use a `Memory` block with a consistent `id` (for example, `chat`) to persist mes
 - Read the conversation history for context
 - Append the Agent's reply after it runs
 
-```yaml
-# 1) Add latest user message
-- Memory (operation: add)
-  id: chat
-  role: user
-  content: {{input}}
-
-# 2) Load conversation history
-- Memory (operation: get)
-  id: chat
-
-# 3) Run the agent with prior messages available
-- Agent
-  System Prompt: ...
-  User Prompt: |
-    Use the conversation so far:
-    {{memory_get.memories}}
-    Current user message: {{input}}
-
-# 4) Store the agent reply
-- Memory (operation: add)
-  id: chat
-  role: assistant
-  content: {{agent.content}}
-```
-
-See the `Memory` block reference for details: [/tools/memory](/tools/memory).
+See the [`Memory`](/tools/memory) block reference for details.
 
 ## Inputs and Outputs
 

apps/docs/content/docs/en/triggers/api.mdx

@@ -24,14 +24,6 @@ The API trigger exposes your workflow as a secure HTTP endpoint. Send JSON data
 
 Add an **Input Format** field for each parameter. Runtime output keys mirror the schema and are also available under `<api.input>`.
 
-```yaml
-- type: string
-  name: userId
-  value: demo-user # optional manual test value
-- type: number
-  name: maxTokens
-```
-
 Manual runs in the editor use the `value` column so you can test without sending a request. During execution the resolver populates both `<api.userId>` and `<api.input.userId>`.
 
 ## Request Example