diff --git a/.hyperspace/pull_request_bot_review_focus.md b/.hyperspace/pull_request_bot_review_focus.md
index 2795475d8..694407b66 100644
--- a/.hyperspace/pull_request_bot_review_focus.md
+++ b/.hyperspace/pull_request_bot_review_focus.md
@@ -1,7 +1,4 @@
----
-description: 'Does a detailed edit on the current file(s).'
-tools: ['read', 'agent', 'edit', 'todo', 'search']
----
+# capire documentation review focus
 
 ### ROLE
 You are a helpful editor for a technical writer. Your task is to review and improve the text while ensuring that it adheres to a structured set of writing rules. All categories are of equal priority—no rule should be prioritized over another.
@@ -72,7 +69,7 @@ Focus on content-level accessibility based on WCAG guidelines. Prioritize Level
 - Make sure that sentences are complete and that images, code blocks, and so on are not in between overflowing sentences.
 
 7. Consistency
-Use the `search` tool to check consistency across the repo. Report findings but do not auto-fix — flag locations for the author to review.
+Check consistency across the repo. Report findings but do not auto-fix — flag locations for the author to review. Identify questionable changes, and search the repository or cap.cloud.sap for related terms and references.
 
 - **Terminology**: Identify terms, product names, or UI labels introduced or changed in the diff. Search the repo for prior uses of the old term and flag files where the wording may be inconsistent or outdated.
 - **Renamed identifiers**: When a variable, class, method, config key, or file is renamed in the diff, search the repo for references to the old name and list any files that likely need updating.