diff --git a/docs/xplat/src/content/en/components/grids/_shared/remote-data-operations.mdx b/docs/xplat/src/content/en/components/grids/_shared/remote-data-operations.mdx
index 99e65fa8b3..41065b76d7 100644
--- a/docs/xplat/src/content/en/components/grids/_shared/remote-data-operations.mdx
+++ b/docs/xplat/src/content/en/components/grids/_shared/remote-data-operations.mdx
@@ -100,7 +100,7 @@ The first <ApiLink type="{ComponentName}" member="chunkSize" /> will always be 0
 
  A popular design for scenarios requiring fetching data by chunks from an end-point is the so-called infinite scroll. For data grids, it is characterized by continuous increase of the loaded data triggered by the end-user scrolling all the way to the bottom. The next paragraphs explain how you can use the available API to easily achieve infinite scrolling in <ApiLink type="{ComponentName}" />.
 
-To implement infinite scroll, you have to fetch the data in chunks. The data that is already fetched should be stored locally and you have to determine the length of a chunk and how many chunks there are. You also have to keep a track of the last visible data row index in the grid. In this way, using the <ApiLink type="ForOfState" member="chunkSize" /> and <ApiLink type="ForOfState" member="chunkSize" /> properties, you can determine if the user scrolls up and you have to show them already fetched data or scrolls down and you have to fetch more data from the end-point.
+To implement infinite scroll, you have to fetch the data in chunks. The data that is already fetched should be stored locally and you have to determine the length of a chunk and how many chunks there are. You also have to keep a track of the last visible data row index in the grid. In this way, using the <ApiLink type="ForOfState" member="chunkSize" /> and <ApiLink type="ForOfState" member="startIndex" /> properties, you can determine if the user scrolls up and you have to show them already fetched data or scrolls down and you have to fetch more data from the end-point.
 
 
 
@@ -884,7 +884,7 @@ We also need to set the method for loading data and update the UI accordingly:
 ```
 
 
-For further reference, please check the demo bellow:
+For further reference, please check the demo below:
 
 ### Grid Remote Paging Demo
 
@@ -946,7 +946,7 @@ After that we just need to bind the paging events to our custom methods, and rem
 }
 ```
 
-For further reference please check the full demo bellow:
+For further reference please check the full demo below:
 
 ### Grid Remote Paging Demo
 
@@ -1018,7 +1018,7 @@ and finally set up the method for loading the data:
   }
 ```
 
-For further reference please check the full sample bellow:
+For further reference please check the full sample below:
 
 ### Grid Remote Paging Demo
 
@@ -1160,7 +1160,7 @@ And finally we need to handle the behaviour behind the actual hierarchy levels o
     }
 ```
 
-For further reference, please check the demo bellow:
+For further reference, please check the demo below:
 
 ### Grid Remote Paging Demo
 
@@ -1222,7 +1222,7 @@ After that we just need to bind the paging events to our custom methods, and rem
 }
 ```
 
-For further reference please check the full demo bellow:
+For further reference please check the full demo below:
 
 ### Grid Remote Paging Demo
 
@@ -1308,8 +1308,8 @@ next set up the method for loading the data:
 </ComponentBlock>
 
 <PlatformBlock for="React">
-and finally set up the behaviour for the RowIslands:
 <ComponentBlock for="HierarchicalGrid">
+and finally set up the behaviour for the RowIslands:
 ```tsx
   function gridCreated(event: IgrGridCreatedEventArgs, parentKey: string) {
     const context = event.detail;
@@ -1343,7 +1343,7 @@ and finally set up the behaviour for the RowIslands:
 ```
 
 
-For further reference please check the full sample bellow:
+For further reference please check the full sample below:
 
 ### Grid Remote Paging Demo
 
@@ -1759,7 +1759,7 @@ As you can see in the <ApiLink type="Paginator" member="paginate" label="Paginat
 
 ## Known Issues and Limitations
 
-- When the grid has no <ApiLink type="{ComponentName}" member="primaryKey" /> set and remote data scenarios are enabled (when paging, sorting, filtering, scrolling trigger requests to a remote server to retrieve the data to be displayed in the grid), a row will lose the following state after a data request completes:
+When the grid has no <ApiLink type="{ComponentName}" member="primaryKey" /> set and remote data scenarios are enabled (when paging, sorting, filtering, scrolling trigger requests to a remote server to retrieve the data to be displayed in the grid), a row will lose the following state after a data request completes:
 
 - Row Selection
 - Row Expand/collapse