[Website]: Context question mark in ingest pipeline example

### Before you submit

- [x] This issue is about a documentation page, flow, or piece of content.

### Type of issue

Inaccurate

### What documentation page or section is affected

https://www.elastic.co/docs/manage-data/ingest/transform-enrich/ingest-pipelines

### What happened?

The example in **Access source fields in a processor** uses `ctx?.network?.name` in the `if` condition.

### Expected behavior

Because `ctx` is always available in an ingest pipeline, the example should not use the safe navigation operator on `ctx`.

### Suggested correction

Update the example to use `ctx.network.name == 'Guest'`.

### Additional info

_No response_

---
🤖 _Refined by RefineBot on 2026-08-11. Original intent preserved._

RefineBot changes

**What changed:**
- Clarified the affected section and the incorrect example behavior.
- Added an expected-behavior section and a concrete suggested correction.
- Kept the original page link and issue intent intact.

**What was preserved:**
- The issue remains classified as an inaccurate documentation report for the ingest pipelines page.
- The original report’s focus on the `ctx?.network?.name` example and its explanation that `ctx` is always available were retained.

**Source:** The target docs page was inspected to confirm the example location and wording.

Previous version

### Before you submit

- [x] This issue is about a documentation page, flow, or piece of content.

### Type of issue

Inaccurate

### What documentation page or section is affected

https://www.elastic.co/docs/manage-data/ingest/transform-enrich/ingest-pipelines

### What happened?

Examples show Question Mark on ctx (Context) that value don't need to have a question mark (Safe Navigation Operator) because Context must be always available.

`PUT _ingest/pipeline/my-pipeline
{
"processors": [
{
"drop": {
"description": "Drop documents with 'network.name' of 'Guest'",
"if": "ctx?.network?.name == 'Guest'"
}
}
]
}`

Please correct this typo on documentation because it is wrong.

### Additional info

_No response_

TriageBot — Needs refinement

### 2026-08-11

**Type:** documentation

**Section check:**
- [✅] type of issue
- [✅] affected page
- [❌] expected behavior: missing explicit expected wording for the correction

**Ambiguity / scope notes:**
- The report says the example is wrong, but the needed correction is implied rather than stated directly.

**Cross-references:**
- All referenced links are valid in the accessible repo context.

**Next step:** Rewritten above
> Generated by [Gh Aw Issue Triage](https://github.com/elastic/docs-content/actions/runs/31513296583) for #7906 · gpt50mini · 5.56 AIC · ⌖ 1.9 AIC · ⊞ 28.6K · [◷](https://github.com/search?q=repo%3Aelastic%2Fdocs-content+is%3Aissue+%22gh-aw-workflow-call-id%3A+elastic%2Fdocs-content%2Fgh-aw-issue-triage%22&type=issues)

Open the linked ingest pipelines documentation page and locate the “Access source fields in a processor” section. Update the example’s condition to remove safe navigation from ctx, then verify that it reads ctx.network.name == 'Guest' and renders correctly.

Written by the indexing model from the issue text.