minimal docs adjustments

Author: ivictbor

adminforth/documentation/docs/tutorial/001-gettingStarted.md

@@ -393,6 +393,7 @@ export default {
       name: 'email',
       required: true,
       isUnique: true,
+      type: AdminForthDataTypes.STRING,
       validation: [
         // you can also use AdminForth.Utils.EMAIL_VALIDATOR which is alias to this object 
         {

adminforth/documentation/docs/tutorial/05-Plugins/10-i18n.md

@@ -387,10 +387,10 @@ If you don't use params, you can use `tr` without third param:
 
 ## Translating messages within bulk action
 
-Label adn confirm strings of bulk actions are already translated by AdminForth, but 
+Label and confirm strings of bulk actions are already translated by AdminForth, but 
 `succesMessage` returned by action function should be translated manually because of the dynamic nature of the message.
 
-Let's rework the bulk action from [bulkActions](/docs/tutorial/Customization/bulkActions/) to use translations:
+Let's rework the bulk action from [bulkActions example](/docs/tutorial/Customization/bulkActions/) to use translations:
 
 ```ts title="./resources/apartments.ts"
 import { AdminUser } from 'adminforth';

adminforth/plugins/i18n/Changelog.md

@@ -5,11 +5,13 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [1.0.22] - next
+## [1.0.22]
 
 ### Fixed
 
 - More predictable class name
+- When loading unique translations from category, they were not registered if existing in other category
+
 
 ## [1.0.21] - 2024-12-30
 

adminforth/plugins/i18n/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@adminforth/i18n",
-  "version": "1.0.22-next.0",
+  "version": "1.0.23-next.0",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "type": "module",
   "scripts": {
     "build": "tsc && rsync -av --exclude 'node_modules' custom dist/",
-    "rollout": "npm run build && npm version patch && npm publish --access public",
+    "rollout": "npm run build && npm version patch && npm publish --access public && npm run rollout-next",
     "rollout-next": "npm run build && npm version prerelease --preid=next && npm publish --tag next",
     "prepare": "npm link adminforth"
   },