Documentation fixes

dev_docs/docs/Fundamentals/Security/authentication/access-token-and-cookie-mixed-auth.md

@@ -1,5 +1,5 @@
 
-Along with JWT access token, Virto manager also uses cookie-based authentication. This additional check is necessary because it is impossible to intercept and inject Authorization header with the token bearer for all API calls requested other than through the [$http](https://docs.angularjs.org/api/ng/service/$http) service. These calls can be produced by other third-party JS components; direct http links and cookie-based authorization are used to solve this problem.
+Along with JWT access token, Virto manager also uses cookie-based authentication. This additional check is necessary because it is impossible to intercept and inject Authorization header with the token bearer for all API calls requested other than through the [$http](https://docs.angularjs.org/api/ng/service/%24http) service. These calls can be produced by other third-party JS components; direct http links and cookie-based authorization are used to solve this problem.
 
 When the user is authorized in the platform, the system intersects all user permissions with the permissions in the `Authorization:LimitedCookiePermissions` configuration section <!---Add link to this section in Configuration reference--> and adds them into cookies along with issuing the JWT token. When the user makes a request to the platform, they are challenged against the helper cookie and the authentication token in accordance with the following rules:
 

user_docs/docs/modules-installation.md

@@ -1,7 +1,7 @@
 
 # Modules Installation
 
-The Modules can be accessed only by admin user who can view view the installed modules, new updates, install new modules or remove the installed ones.
+The Modules can be accessed only by admin user who can view the installed modules, new updates, install new modules or remove the installed ones.
 
 Clicking the **Modules** in the main menu opens the **Modules** blade: