[blakeaowens]

Description

Fixes five out-of-date places in the docs:

• API v2 Sample Code (automation/api/api-v2-docs.md): both Python samples now query /api/v2/findings/, which any token can read (the old /users/ sample returned 403 for a Reader). They call raise_for_status(), print each finding's id and title instead of the Response object's internals, and use a placeholder host and <Your API Token>. The second sample filters on severity and active, notes that severity values are case-sensitive, and shows the paginated response shape (count, next, previous, prefetch, results) with limit and offset.
• do_not_reactivate (same page, Reimport): a reimport keeps a closed finding closed when it appears in the report again and adds a note to it; new findings are still created and open findings are processed as usual.
• Location Map (PRO__location_map.md, PRO__locations_overview.md): linked from the Locations overview, with the relationship editing wording corrected (Clear is an option in the picker, then Save) and what a Reader cannot change stated.
• Location page (PRO__working_with_urls.md): its table is Affected Open Findings, filtered on Status Active. The page now says how to see every finding on a Location: the Total Findings count in a list of Locations opens the Findings list filtered to it.
• Upstream records screenshots (edit_ignore_delete_records.png, edit_ignore_delete_records_2.png): recaptured from demo data, so the first shows the row menu the text describes.

English pages and images only; the language copies are generated.

Test results

Docs only. Both samples were run against a local instance with a Reader's token, and the Location statements were checked in the running app as an administrator and as a Reader. Every link and image path resolves.

Documentation

This PR is the documentation change.

Checklist

• Make sure to rebase your PR against the very latest dev.
• Submit all PRs, features and bug fixes alike, against the dev branch.
• Give a meaningful name to your PR, as it may end up being used in the release notes.
• Your code is Ruff compliant (see ruff.toml).
• Your code is python 3.13 compliant.
• If this is a new feature and not a bug fix, you've included the proper documentation in the docs at https://github.com/DefectDojo/django-DefectDojo/tree/dev/docs as part of this PR.
• Model changes must include the necessary migrations in the dojo/db_migrations folder.
• Add applicable tests to the unit tests.
• Add the proper label to categorize your PR.

🤖 Generated with Claude Code