docs: update documentation to reflect changes in user and system Data API methods

Author: yaroslav8765

documentation/docs/tutorial/03-Customization/12-security.md

@@ -118,7 +118,7 @@ This is opt-in. It is especially important for the column configured as `auth.us
 
 | Path | When `normalize` runs |
 | --- | --- |
-| User-scoped Data API (`admin.resource(...).asUser(...)`) and `admin.createResourceRecord` | Before validation and `beforeSave` hooks |
+| User-scoped and system Data API (`admin.resource(...).asUser(...)`, `admin.resource(...).asSystem(...)`) | Before validation and `beforeSave` hooks |
 | Bare Data API (`admin.resource(...).create(...)` and siblings) | Before the connector operation |
 | Deprecated AdminForth CRUD (`createResourceRecord`, `updateResourceRecord`) | Before validation and `beforeSave` hooks |
 | Core password login | On the submitted value of `auth.usernameField`, before the user lookup |

documentation/docs/tutorial/03-Customization/13-standardPagesTuning.md

@@ -1054,7 +1054,7 @@ If `beforeDatasourceRequest` or `afterDatasourceResponse` hooks are set for poly
 In cases when column values must follow certain format, you can add `validation` to it.
 `validation` is an array of rules, each containing `regExp` or `validator function` that defines a format for a value and `message` that will be displayed in case when entered value does not pass the check.
 
-The create and edit forms check `validation`, `required`, `minLength`/`maxLength`, `minValue`/`maxValue`, `enum` values and `isArray` rules while the user types. The server checks all of them again when the record is saved, so a request sent past the form cannot store an invalid value. `required` columns hidden by `showIn` or `showIf` are not required. Records created or updated from code with `createResourceRecord`/`updateResourceRecord` go through the same checks except `required`.
+The create and edit forms check `validation`, `required`, `minLength`/`maxLength`, `minValue`/`maxValue`, `enum` values and `isArray` rules while the user types. The server checks all of them again when the record is saved, so a request sent past the form cannot store an invalid value. `required` columns hidden by `showIn` or `showIf` are not required. Records created or updated from code with `admin.resource(...).asUser(...)` or `admin.resource(...).asSystem(...)` go through the same checks except `required`.
 
 ### RegExp validation
 We recommend to use this validation with regExp, because it validates fields in real time