diff --git a/docs/framework/alpine/guide/pagination.md b/docs/framework/alpine/guide/pagination.md
index d766d126be..50799da056 100644
--- a/docs/framework/alpine/guide/pagination.md
+++ b/docs/framework/alpine/guide/pagination.md
@@ -84,7 +84,7 @@ No pagination row model is needed for server-side pagination, but if you have pr
 
 #### Page Count and Row Count
 
-The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case.
+The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but in that case `getCanNextPage` will always return `true`. `getCanPreviousPage` does not read `pageCount` at all: it only checks whether the current `pageIndex` is greater than `0`.
 
 ```ts
 import {
diff --git a/docs/framework/angular/guide/pagination.md b/docs/framework/angular/guide/pagination.md
index 5d12b7f24d..7e752837a6 100644
--- a/docs/framework/angular/guide/pagination.md
+++ b/docs/framework/angular/guide/pagination.md
@@ -89,7 +89,7 @@ No pagination row model is needed for server-side pagination, but if you have pr
 
 #### Page Count and Row Count
 
-The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case.
+The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but in that case `getCanNextPage` will always return `true`. `getCanPreviousPage` does not read `pageCount` at all: it only checks whether the current `pageIndex` is greater than `0`.
 
 ```ts
 import {
diff --git a/docs/framework/ember/guide/pagination.md b/docs/framework/ember/guide/pagination.md
index 8b14cb1ce9..e3905bf316 100644
--- a/docs/framework/ember/guide/pagination.md
+++ b/docs/framework/ember/guide/pagination.md
@@ -84,7 +84,7 @@ No pagination row model is needed for server-side pagination, but if you have pr
 
 #### Page Count and Row Count
 
-The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case.
+The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but in that case `getCanNextPage` will always return `true`. `getCanPreviousPage` does not read `pageCount` at all: it only checks whether the current `pageIndex` is greater than `0`.
 
 ```ts
 import {
diff --git a/docs/framework/lit/guide/pagination.md b/docs/framework/lit/guide/pagination.md
index 5119b3a845..1fe314e929 100644
--- a/docs/framework/lit/guide/pagination.md
+++ b/docs/framework/lit/guide/pagination.md
@@ -98,7 +98,7 @@ No pagination row model is needed for server-side pagination, but if you have pr
 
 #### Page Count and Row Count
 
-The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case.
+The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but in that case `getCanNextPage` will always return `true`. `getCanPreviousPage` does not read `pageCount` at all: it only checks whether the current `pageIndex` is greater than `0`.
 
 ```ts
 import {
diff --git a/docs/framework/octane/guide/pagination.md b/docs/framework/octane/guide/pagination.md
index 9f63a5be17..b6f000ac82 100644
--- a/docs/framework/octane/guide/pagination.md
+++ b/docs/framework/octane/guide/pagination.md
@@ -84,7 +84,7 @@ No pagination row model is needed for server-side pagination, but if you have pr
 
 #### Page Count and Row Count
 
-The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case.
+The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but in that case `getCanNextPage` will always return `true`. `getCanPreviousPage` does not read `pageCount` at all: it only checks whether the current `pageIndex` is greater than `0`.
 
 ```tsx
 import {
diff --git a/docs/framework/preact/guide/pagination.md b/docs/framework/preact/guide/pagination.md
index b9826208f6..560206ecc8 100644
--- a/docs/framework/preact/guide/pagination.md
+++ b/docs/framework/preact/guide/pagination.md
@@ -84,7 +84,7 @@ No pagination row model is needed for server-side pagination, but if you have pr
 
 #### Page Count and Row Count
 
-The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case.
+The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but in that case `getCanNextPage` will always return `true`. `getCanPreviousPage` does not read `pageCount` at all: it only checks whether the current `pageIndex` is greater than `0`.
 
 ```tsx
 import {
diff --git a/docs/framework/react/guide/pagination.md b/docs/framework/react/guide/pagination.md
index 93cb500f97..1d0da82acf 100644
--- a/docs/framework/react/guide/pagination.md
+++ b/docs/framework/react/guide/pagination.md
@@ -84,7 +84,7 @@ No pagination row model is needed for server-side pagination, but if you have pr
 
 #### Page Count and Row Count
 
-The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case.
+The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but in that case `getCanNextPage` will always return `true`. `getCanPreviousPage` does not read `pageCount` at all: it only checks whether the current `pageIndex` is greater than `0`.
 
 ```tsx
 import {
diff --git a/docs/framework/solid/guide/pagination.md b/docs/framework/solid/guide/pagination.md
index dc05192789..68a3c39904 100644
--- a/docs/framework/solid/guide/pagination.md
+++ b/docs/framework/solid/guide/pagination.md
@@ -88,7 +88,7 @@ No pagination row model is needed for server-side pagination, but if you have pr
 
 #### Page Count and Row Count
 
-The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case.
+The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but in that case `getCanNextPage` will always return `true`. `getCanPreviousPage` does not read `pageCount` at all: it only checks whether the current `pageIndex` is greater than `0`.
 
 ```tsx
 import {
diff --git a/docs/framework/svelte/guide/pagination.md b/docs/framework/svelte/guide/pagination.md
index 2ea77d6821..769f21e16b 100644
--- a/docs/framework/svelte/guide/pagination.md
+++ b/docs/framework/svelte/guide/pagination.md
@@ -88,7 +88,7 @@ No pagination row model is needed for server-side pagination, but if you have pr
 
 #### Page Count and Row Count
 
-The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case.
+The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but in that case `getCanNextPage` will always return `true`. `getCanPreviousPage` does not read `pageCount` at all: it only checks whether the current `pageIndex` is greater than `0`.
 
 ```ts
 import {
diff --git a/docs/framework/vue/guide/pagination.md b/docs/framework/vue/guide/pagination.md
index 9487df9f53..d916247b34 100644
--- a/docs/framework/vue/guide/pagination.md
+++ b/docs/framework/vue/guide/pagination.md
@@ -86,7 +86,7 @@ No pagination row model is needed for server-side pagination, but if you have pr
 
 #### Page Count and Row Count
 
-The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but the `getCanNextPage` and `getCanPreviousPage` row model functions will always return `true` in this case.
+The table instance will have no way of knowing how many rows/pages there are in total in your back-end unless you tell it. Provide either the `rowCount` or `pageCount` table option to let the table instance know how many pages there are in total. If you provide a `rowCount`, the table instance will calculate the `pageCount` internally from `rowCount` and `pageSize`. Otherwise, you can directly provide the `pageCount` if you already have it. If you don't know the page count, you can just pass in `-1` for the `pageCount`, but in that case `getCanNextPage` will always return `true`. `getCanPreviousPage` does not read `pageCount` at all: it only checks whether the current `pageIndex` is greater than `0`.
 
 ```ts
 import {