docs(search): keep the untouched neighbour lines byte-identical

Re-wrap the two edits so error-handling's parenthesis and query-syntax's
paragraph change only the lines that carry the new text.

Claude-Session: https://claude.ai/code/session_01FM29ZqLTrnPNXxijioZwMp
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

content/docs/protocol/kernel/error-handling.mdx

@@ -624,8 +624,8 @@ knows which object was addressed.
 
 The [error catalog's `INVALID_FIELD` entry](/docs/api/error-catalog#invalid_field) carries
 the authoritative cause text — it enumerates every read axis this one code answers on
-(`select`, `expand`, `search`, `searchFields`, `groupBy`, `aggregations[].field`) and
-the off-request `backfillSummaryNulls` case.
+(`select`, `expand`, `search`, `searchFields`, `groupBy`, `aggregations[].field`) and the
+off-request `backfillSummaryNulls` case.
 
 ### Resource Errors
 

content/docs/protocol/objectql/query-syntax.mdx

@@ -1128,8 +1128,8 @@ the tolerant intersection, but not a search with nothing to scan: when no
 `searchableFields` entry names a stored field and the auto-default finds none
 (`internal: true` fields never count), the engine itself refuses a non-blank `search`
 with `400 INVALID_FIELD` (`param: 'search'`) on `find`, `findOne`, `count` and
-`aggregate` alike, rather than answering every row. Multiple whitespace-separated
-terms are AND-ed and fields are OR-ed. Case sensitivity comes from the operator the expansion emits, not
+`aggregate` alike, rather than answering every row. Multiple whitespace-separated terms are AND-ed and
+fields are OR-ed. Case sensitivity comes from the operator the expansion emits, not
 from the expansion: it emits `$icontains`, which ignores **ASCII case** by the
 rule in [Case Sensitivity](#case-sensitivity) above. So a user typing `acme` does
 find `ACME Corp` — search is case-insensitive by ruling