update protecting a list endpoint

Author: miparnisari

app/spicedb/concepts/querying-data/page.mdx

@@ -37,7 +37,7 @@ It's always preferable to perform one call to `CheckBulkPermissions` with N chec
 
 [`LookupResources`](https://buf.build/authzed/api/docs/main:authzed.api.v1#authzed.api.v1.PermissionsService.LookupResources) is a good choice when you need to find all resources of a given type that a specific subject can access. It supports cursoring and works well for moderate result sizes.
 
-If you’re expecting more than ~10,000 results, this isn't ideal. See [this](../modeling/protecting-a-list-endpoint) for more details.
+If you’re expecting more than ~10,000 results, this isn't ideal. See [this](../modeling/protecting-a-list-endpoint#checking-with-checkbulkpermissions) for more details.
 
 [Materialize]: /authzed/concepts/authzed-materialize
 

app/spicedb/modeling/protecting-a-list-endpoint/page.mdx

@@ -23,7 +23,7 @@ your API, in addition to the overall size of your data.
 
 ## Filtering with LookupResources
 
-If the number of resources that a user has access to is sufficiently small, you can use the [`LookupResources`] API to get the full
+If the number of resources that a user has access to is small (e.g. less than 10,000 resources), you can use the [`LookupResources`] API to get the full
 list of resources for which a user has a particular permission, and then use that as a filtering clause in your database
 query.
 In python pseudocode: