PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/main/contributing-docs/commit-message-guidelines.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.dev application / infrastructure changes
• Other... Please describe:

What is the current behavior?

In the resource usage example within the "Aborting requests" section of the signals/resource.md guide, the destructured parameter is incorrectly named request.

loader: ({request, abortSignal}) => fetch(`users/${request.id}`, { signal: abortSignal });

This is inconsistent with the expected ResourceLoaderParams type, which defines the field as params.

Issue Number: N/A

What is the new behavior?

The code example now correctly uses:

loader: ({params, abortSignal}) => fetch(`users/${params.id}`, { signal: abortSignal });

This change aligns the example with the actual resource API and avoids potential confusion or incorrect usage.

Does this PR introduce a breaking change?

• Yes
• No

Other information