docs: adjust intial pages

Author: ivictbor

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

@@ -77,7 +77,7 @@ myadmin/
 
 ### Initial Migration & Future Migrations
 
-> ☝️ CLI creates Prisma schema file for managing migrations in relational databases, however you are not forced to use it. Instead you are free to use your favourite or existing migration tool. In this case just ignore generated prisma file, and don't run migration command which will be suggested by CLI. However you have to ensure that your migration tool will generate required table `adminuser` with same fields and types for Users resource.
+> ☝️ CLI creates Prisma schema file for managing migrations in relational databases, however you are not forced to use it. Instead you are free to use your favourite or existing migration tool. In this case just ignore generated prisma file, and don't run migration command which will be suggested by CLI. However you have to ensure that your migration tool will generate required table `adminuser` with same fields and types for Admin Users resource to implmenet BackOffice authentication.
 
 CLI will suggest you a command to initialize the database with Prisma:
 

adminforth/documentation/docs/tutorial/01-helloWorld.md

@@ -343,6 +343,9 @@ cd ./custom
 npm init -y
 ```
 
+We will use this directory for all custom components. If you want to call your dir with other name then `custom`, just set [customComponentsDir option](/docs/api/Back/interfaces/AdminForthConfigCustomization/#customcomponentsdir)
+
+
 Also, for better development experience we recommend to create file `custom/tsconfig.json` with the following content:
 
 ```json

adminforth/documentation/docs/tutorial/02-glossary.md

@@ -9,13 +9,12 @@ It used to:
 * Make queries to get the list and show records
 * Make queries to modify data
 
-There might be several datasources in the system for various databases e.g. One 2 Mongo DBs and 1 Postgres DB. 
+There might be several datasources in the system for various databases e.g. One datasource to Mongo DBs and one to Postgres DB. 
 
 ## resource
 
-A [Resource](/docs/api/Back/interfaces/AdminForthResource.md) is a representation of a table or collection in AdminForth. One resource is one table in the database.
-It has a `name` which should match name in database, a datasource id, and a list of columns.
-Also it has various customization options. 
+A [Resource](/docs/api/Back/interfaces/AdminForthResource.md) is a AdminForth representation of a table or collection in database. One resource is one table in the database. Resource has `table` property which should be equal to the name of the table in the database.
+It has a datasource id to point to database, a  definition of list of columns and various customization options. 
 
 ## column
 
@@ -47,6 +46,7 @@ There are next [actions](/docs/api/Common/enumerations/AllowedActionsEnum.md):
 
 Hook is a optional async function which allows to inject in backend logic before executing the datasource query or after it. 
 Hooks exist for all database queries including data read queries like list, show, and data write queries like create, edit, delete.
+All AdminForth hooks are executed on the backend side only.
 
 ## allowedAction
 
@@ -56,8 +56,16 @@ returned false you can be sure that user attempt to perform the action or get th
 
 ## component
 
-Component is a Vue component which is used to add or modify UI elements in AdminForth. It can be used as a full custom page with a link in menu or as a part of the existing AdminForth page
+Component is a Vue frontend component which is used to add or modify UI elements in AdminForth. It can be used as a full custom page with a link in menu or as a part of the existing AdminForth page
 
 ## field
 
-The column in the record.
+Same to column, but considered in context of record.
+
+## Plugin
+
+Plugin is a class defined to extend AdminForth functionality. Plugin philosophy is to simply modify AdminForth config after it is defined by user. In other words, everything that could be done in config, can be done in plugin and vice versa.
+
+In same way, like config does it, plugins set own Frontend components and backend hooks to modify AdminForth behavior.
+
+The main difference is that plugin allows to simplify routine repeating tasks and reduce the amount of code in the config file and code of cusomtom components.

adminforth/documentation/docs/tutorial/03-Customization/01-branding.md

@@ -6,15 +6,9 @@ image: "/ogs/branding.png"  # Path to the OG image
 
 # Branding and Theming
 
-The first things you would probably like to change are the logo, favicon and the name of the application. 
+The first things you would probably like to change are the logo, favicon and the name of the admin application. 
 
-First of all create directory named `custom` at the same level with your TypeScript/JavaScript index file. 
-
-We will use this directory for all custom components. If you want to call your dir with other name then `custom`, just set [customComponentsDir option](/docs/api/Back/interfaces/AdminForthConfigCustomization/#customcomponentsdir)
-
-Place your logo file into the `custom` directory e.g. (`logo.svg`)
-
-Also place your favicon into the `custom` directory e.g. (`favicon.png`)
+You can place your logo and favicon files into the `custom` directory e.g. replacing existing default `logo.svg` and `favicon.png` files.
 
 Then you can change the branding of the application in the configuration:
 
@@ -49,7 +43,6 @@ You can use `@@/` prefix for all paths in the configuration and also import imag
 
 ## Removing brand name from sidebar
 
-
 If you are using logo image which has branded title inside, you might
 want completely remove default text brand name from sidebar:
 
@@ -102,7 +95,6 @@ Here is how it looks:
 ![AdminForth Themes](image-10.png)
 
 
-
 ## Square vs rounded buttons?
 
 Not an issue, just change: