tidy up release notes to not have full error per feedback

Author: mrjones-plip

content/en/releases/5_0_3.md

@@ -10,18 +10,7 @@ description:
 
 ## Highlights
 
-This release fixes a bug when an instance has one or more users with a large amount of documents (over 150,000).  Deployments that suffer from this bug will see an error in the API logs:
-
-```
-2026-04-01T06:30:14.828 ERROR: Server error: RangeError: Maximum call stack size exceeded
-    at getDocsByReplicationKeyNouveau (/service/api/src/services/authorization.js:640:10)
-    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
-    at async Object.getContext (/service/api/src/services/replication.js:10:32)
-    at async getDocIds (/service/api/src/controllers/replication.js:7:23) {
-  [stack]: [Getter/Setter],
-  [message]: 'Maximum call stack size exceeded'
-} 
-```
+This release fixes a bug when an instance has one or more users with a large amount of documents (over 150,000).  Deployments that suffer from this bug will see an error in the API logs (`Maximum call stack size exceeded`).  See the ticket below for more details.
 
 ### Bug fixes
 

content/en/releases/5_1_1.md

@@ -10,18 +10,7 @@ description:
 
 ## Highlights
 
-This release fixes a bug when an instance has one or more users with a large amount of documents (over 150,000).  Deployments that suffer from this bug will see an error in the API logs:
-
-```
-2026-04-01T06:30:14.828 ERROR: Server error: RangeError: Maximum call stack size exceeded
-    at getDocsByReplicationKeyNouveau (/service/api/src/services/authorization.js:640:10)
-    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
-    at async Object.getContext (/service/api/src/services/replication.js:10:32)
-    at async getDocIds (/service/api/src/controllers/replication.js:7:23) {
-  [stack]: [Getter/Setter],
-  [message]: 'Maximum call stack size exceeded'
-} 
-```
+This release fixes a bug when an instance has one or more users with a large amount of documents (over 150,000).  Deployments that suffer from this bug will see an error in the API logs (`Maximum call stack size exceeded`).  See the ticket below for more details.
 
 ### Bug fixes