remove over explanation

Author: DavudSafarli

docs/keto/guides/strict-mode.mdx

@@ -30,7 +30,7 @@ Strict mode improves both performance and correctness:
 Ory Network enforces fixed depth and width limits that cannot be changed in the console. If you hit a limit, contact
 [Ory support](https://www.ory.com/support) to discuss your use case.
 
-## Known breaking patterns
+## Patterns that break in strict mode
 
 These patterns work in non-strict mode but break after enabling strict mode.
 

docs/keto/reference/ory-permission-language.mdx

@@ -96,8 +96,6 @@ class File implements Namespace {
 
 `this.related.x.traverse(g => ...)` iterates over the objects in relation `x` and evaluates the inner expression for each one.
 
-**Check via a relation on the related object:**
-
 ```ts
 class Group implements Namespace {
   related: {
@@ -117,31 +115,6 @@ class File implements Namespace {
 
 `view` is granted if the subject is a member of any group in `viewerGroups`.
 
-**Check via a permission on the related object:**
-
-```ts
-class Group implements Namespace {
-  related: {
-    members: User[]
-  }
-  permits = {
-    isMember: (ctx: Context) => this.related.members.includes(ctx.subject),
-  }
-}
-
-class File implements Namespace {
-  related: {
-    viewerGroups: Group[]
-  }
-  permits = {
-    view: (ctx: Context) => this.related.viewerGroups.traverse((g) => g.permits.isMember(ctx)),
-  }
-}
-```
-
-Same result, but delegating to a named permission on `Group` instead of accessing the relation directly. Use this when the
-permission logic on the related namespace is more complex than a single `includes` check.
-
 ### Boolean operators
 
 Combine checks with `||`, `&&`, and `!`: