fix spelling

Author: mvorisek

README.md

@@ -229,7 +229,7 @@ Agile Data has a usage patters that will automatically restrict access by this c
 
 With Agile Data you can move your data from one persistence to another seamlessly. If you rely on some feature that your new persistence does not support (e.g. Expression) you can replace them a callback calculation, that executes on your App server.
 
-As usual - the rest of your application is not affected and you can even use multiple types of different persistences and still navigate through references.
+As usual - the rest of your application is not affected and you can even use multiple types of different persistencies and still navigate through references.
 
 #### Support
 

docs/design.rst

@@ -516,7 +516,7 @@ So getting back to the operation above, lets look at it in more details::
 
 While "vip_orders" is actually a DataSet, executing count() will cross you over
 into persistence layer. However this method is returning a new object, which is then
-executed when you call getOne(). For SQL persistences it returns \Atk4\Data\Persistence\Sql\Query
+executed when you call getOne(). For SQL persistencies it returns \Atk4\Data\Persistence\Sql\Query
 object, for example.
 
 Even though for a brief moment you had your hands on a "database-vendor specific"

docs/overview.rst

@@ -47,7 +47,7 @@ basic functionality is divided into 3 major areas:
 
  - Fields (or Columns)
  - DataSets (or Rows)
- - Databases (or Persistences)
+ - Databases (or Persistencies)
 
 Each of the above corresponds to a PHP class, which may use composition principle
 to hide implementation details.
@@ -171,7 +171,7 @@ MongoDB), you would need to define the field differently::
     });
 
 When you use persistence-specific code, you must be aware that it will not map
-into persistences that does not support features you have used.
+into persistencies that does not support features you have used.
 
 In most cases that is OK as if you prefer to stay with same database type, for
 instance, the above expression will still be usable with any SQL vendor, but if
@@ -217,7 +217,7 @@ Persistence Scaling
 ===================
 
 Although in most cases you would be executing operation against SQL persistence,
-Agile Data makes it very easy to use models with a simpler persistences.
+Agile Data makes it very easy to use models with a simpler persistencies.
 
 For example, consider you want to output a "table" to the user using HTML by
 using Agile UI::
@@ -229,7 +229,7 @@ using Agile UI::
 
     echo $htmltable->render();
 
-Class `\\Atk4\\Ui\\Table` here is designed to work with persistences and models -
+Class `\\Atk4\\Ui\\Table` here is designed to work with persistencies and models -
 it will populate columns of correct type, fetch data, calculate totals if needed.
 But what if you have your data inside an array?
 You can use :php:class:`Persistence\Static_` for that::

docs/persistence.rst

@@ -544,7 +544,7 @@ The other, more appropriate option is to re-use a vanilla Order record::
     }
 
 
-Working with Multiple Persistences
+Working with Multiple Persistencies
 ==================================
 
 Normally when you load the model and save it later, it ends up in the same
@@ -573,7 +573,7 @@ Agile Data, so you will have to create logic yourself, which is actually quite
 simple.
 
 You can use several designs. I will create a method inside my application class
-to load records from two persistences that are stored inside properties of my
+to load records from two persistencies that are stored inside properties of my
 application::
 
     function loadQuick($class, $id) {

docs/references.rst

@@ -51,7 +51,7 @@ model that has a persistence set. (See Reference::getModel())
 Persistence
 -----------
 
-Agile Data supports traversal between persistences. The code above does not
+Agile Data supports traversal between persistencies. The code above does not
 explicitly assign database to Model_Order. But what if destination model does
 not reside inside the same database?
 

docs/sql.rst

@@ -329,7 +329,7 @@ procedures you will loose portability of your application.
 
 We do have our legacy applications to maintain, so Stored Procedures and SQL
 extensions are here to stay. By making your Model rely on those extensions you
-will loose ability to use the same model with non-sql persistences.
+will loose ability to use the same model with non-sql persistencies.
 
 Sometimes you can fence the code like this::
 
@@ -338,7 +338,7 @@ Sometimes you can fence the code like this::
     }
 
 Or define your pure model, then extend it to add SQL capabilities. Note that
-using single model with cross-persistences should still be possible, so you
+using single model with cross-persistencies should still be possible, so you
 should be able to retrieve model data from stored procedure then cache it.
 
 as a Model method

docs/typecasting.rst

@@ -144,7 +144,7 @@ Field may use serialization to further encode field value for the storage purpos
 Array and Object types
 ----------------------
 
-Some types may require serialization for some persistences, for instance types
+Some types may require serialization for some persistencies, for instance types
 'json' and 'object' cannot be stored in SQL natively. `json` type can be used
 to store these in JSON.
 

src/Persistence.php

@@ -103,7 +103,7 @@ protected function initPersistence(Model $m): void
 
     /**
      * Atomic executes operations within one begin/end transaction. Not all
-     * persistences will support atomic operations, so by default we just
+     * persistencies will support atomic operations, so by default we just
      * don't do anything.
      *
      * @return mixed
@@ -195,7 +195,7 @@ public function typecastSaveRow(Model $model, array $row): array
      * types to PHP native types.
      *
      * NOTE: Please DO NOT perform "actual" field mapping here, because data
-     * may be "aliased" from SQL persistences or mapped depending on persistence
+     * may be "aliased" from SQL persistencies or mapped depending on persistence
      * driver.
      */
     public function typecastLoadRow(Model $model, array $row): array