diff --git a/src/docs/apex-import.md b/src/docs/apex-import.md
index 3bb33b4..7bb5260 100644
--- a/src/docs/apex-import.md
+++ b/src/docs/apex-import.md
@@ -2,7 +2,7 @@
 
 Using Apex in LWC Offline-enabled mobile apps requires additional considerations to ensure proper functioning in offline scenarios. Consider using GraphQL for mobile offline use cases.
 
-GraphQL is a flexible, powerful query language for accessing record and other data. You can think of GraphQL as a modern equivalent of SQL, the query language for relational databases.
+GraphQL is a flexible, powerful query language for accessing record and other data. You can think of GraphQL as SQL for your API, the query language for relational databases.
 
 Developers like GraphQL for modern web applications because, in contrast to many REST and CRUD-oriented APIs, GraphQL allows for expressive queries, with features like filtering and scopes, ordering and aggregation, pagination, and relationship traversal to related records. A single query can retrieve many records, and even records of multiple types. Using fewer queries reduces the number of server requests required to load data, which can improve performance. A GraphQL query can specify precisely and only the fields required for a given component, reducing the amount of data that needs to be transmitted before a page can render.
 
diff --git a/src/docs/no-more-than-100-fields.md b/src/docs/no-more-than-100-fields.md
index 5837d3b..4622276 100644
--- a/src/docs/no-more-than-100-fields.md
+++ b/src/docs/no-more-than-100-fields.md
@@ -2,9 +2,6 @@
 
 This rule flags entities with more than 100 fields. If a root entity query has more than 100 fields and requests over 200 records, the query is capped to 200 records.
 
-See [Feature Limitations of Offline GraphQL
-](https://developer.salesforce.com/docs/atlas.en-us.mobile_offline.meta/mobile_offline/use_graphql_limitations.htm) for more details.
-
 ## ❌ Incorrect
 
 ```GraphQL