docs: resolve conflicts

Signed-off-by: memleakd <121398829+memleakd@users.noreply.github.com>

Author: memleakd

user_guide_src/source/models/model.rst

@@ -1044,7 +1044,7 @@ If you need to update or delete rows while processing them, use ``chunkById()``.
 This method retrieves each chunk ordered by the model's primary key instead of using an offset,
 so deleting or updating rows already processed will not cause later rows to be skipped.
 
-.. literalinclude:: model/069.php
+.. literalinclude:: model/071.php
 
 chunkRowsById()
 ---------------
@@ -1053,7 +1053,7 @@ chunkRowsById()
 
 If you want the entire ID-based chunk to be passed to the Closure at once, use ``chunkRowsById()``.
 
-.. literalinclude:: model/070.php
+.. literalinclude:: model/072.php
 
 .. warning:: ID-based chunking needs the model to define a primary key, and that primary key must be selected.
     If you customize the selected columns, make sure the primary key is included.

user_guide_src/source/models/model/070.php

@@ -1,7 +1,7 @@
 <?php
 
 $userModel->where('country', 'US')
-    ->chunkRowsById(100, static function ($rows) {
+    ->chunkById(100, static function ($data) {
         // do something.
-        // $rows is an array of rows representing a chunk of 100 items.
+        // $data is a single row of data.
     });

user_guide_src/source/models/model/071.php

@@ -0,0 +1,7 @@
+<?php
+
+$userModel->where('country', 'US')
+    ->chunkRowsById(100, static function ($rows) {
+        // do something.
+        // $rows is an array of rows representing a chunk of 100 items.
+    });