Audit Logging Module document.

docs/en/Modules/Audit-Logging.md

@@ -1,3 +1,7 @@
 # Audit Logging Module
 
-TODO
+The Audit Logging Module basically implements the `IAuditingStore` to save the audit log objects to a database. 
+
+> Audit Logging module is already installed and configured for [the startup templates](../Startup-Templates/Index.md). So, most of the times you don't need to manually add this module to your application.
+
+See [the audit logging system](../Audit-Logging.md) document for more about the audit logging.

docs/en/Modules/Index.md

@@ -11,16 +11,20 @@ There are **two types of modules.** They don't have any structural difference bu
 
 There are some **free and open source** application modules developed and maintained by the ABP community:
 
-* **Account**: Used to make user login/register to the application.
-* **Audit Logging**: Used to persist audit logs to a database.
-* **Background Jobs**: Used to persist background jobs when using default background job manager.
+* **Account**: Provides UI for the account management and allows user to login/register to the application.
+* [**Audit Logging**](Audit-Logging.md): Persists audit logs to a database.
+* **Background Jobs**: Persist background jobs when using the default background job manager.
 * **Blogging**: Used to create fancy blogs. ABP's [own blog](https://abp.io/blog/abp/) already using this module.
 * [**Docs**](Docs.md): Used to create technical documentation pages. ABP's [own documentation](https://docs.abp.io) already using this module.
-* **Identity**: Used to manage roles, users and their permissions.
+* **Identity**: Manages roles, users and their permissions, based on the Microsoft Identity library.
 * **IdentityServer**: Integrates to IdentityServer4.
 * **Permission Management**: Used to persist permissions.
 * **[Setting Management](Setting-Management.md)**: Used to persist and manage the [settings](../Settings.md).
-* **Tenant Management**: Used to manage tenants for a [multi-tenant](../Multi-Tenancy.md) application.
-* **Users**: Used to abstract users, so other modules can depend on this instead of the Identity module.
+* **Tenant Management**: Manages tenants for a [multi-tenant](../Multi-Tenancy.md) application.
+* **Users**: Abstract users, so other modules can depend on this module instead of the Identity module.
 
-Documenting the modules is in the progress. See [this repository](https://github.com/abpframework/abp/tree/master/modules) for source code of all modules.
+See [the GitHub repository](https://github.com/abpframework/abp/tree/master/modules) for source code of all modules.
+
+## Commercial Application Modules
+
+[ABP Commercial](https://commercial.abp.io/) license provides additional pre-built application modules on top of the ABP framework. See the [module list](https://commercial.abp.io/modules) provided by the ABP Commercial.

docs/en/Modules/Setting-Management.md

@@ -67,6 +67,8 @@ namespace Demo
 
 So, you can get or set a setting value for different setting value providers (Default, Global, User, Tenant... etc).
 
+> Use the `ISettingProvider` instead of the `ISettingManager` if you only need to read the setting values, because it implements caching and supports all deployment scenarios. You can use the `ISettingManager` if you are creating a setting management UI.
+
 ### Setting Cache
 
 Setting values are cached using the [distributed cache](../Caching.md) system. Always use the `ISettingManager` to change the setting values which manages the cache for you.