fixed scan links and env example

Author: amaksimovv

docs/agent/scan.en.md

@@ -12,7 +12,7 @@ The agent is launched using the `scan` command with possible scanning options:
 - `scan image` – [scanning a container image](/agent/scan-docker.en);
 - `scan bom` – [scanning a SBOM](/agent/scan-bom.en);
 - `scan <technology>` - [scanning a directory using settings for selected technology](/agent/scan-technology.en);
-- `scan build` – [scanning a build](agent/scan-build.en).
+- `scan build` – [scanning a build](/agent/scan-build.en).
 
 ## Launch options
 

docs/agent/scan.md

@@ -12,7 +12,7 @@ hide:
 - `scan image` – [сканирование контейнерного образа](/agent/scan-docker);
 - `scan bom` – [сканирование SBOM](/agent/scan-bom);
 - `scan <technology>` - [сканирование директории с применением настроек для указанной технологии](/agent/scan-technology);
-- `scan build` – [сканирование сборки](agent/scan-build).
+- `scan build` – [сканирование сборки](/agent/scan-build).
 
 ## Опции запуска
 

docs/on-premise/installation.en.md

@@ -19,14 +19,14 @@ hide:
 
 6. Copy the template file with secrets:
 
-      ```
-      cp.env.template.env
+      ```bash
+      cp .env.template .env
       ```
     If necessary, configure settings in a new file.
     If you do not change the parameters in the file, then by default the system will be available at `http://localhost:8081`.
 
       - List of domains for proper operation of CSRF protection. It is recommended to list localhost on the internal and external ports, as well as the external domain (or ip:port combination). Specifying the protocol is mandatory, for example:
-       - `DJANGO_CSRF_TRUSTED_ORIGINS=http://localhost:18000,https://localhost:8081,https://external ip:8081`
+       - `DJANGO_CSRF_TRUSTED_ORIGINS=http://localhost:18000,https://localhost:8081,https://example.com:8081`
       - Connection parameters to the PostgreSQL database. The database is supplied with the platform. Specifying accesses separately is a precaution and control measure. When using your own database, you must ensure that it corresponds to [requirements](/on-premise/server-requirements.en/#supported-versions-of-external-services).
         - `POSTGRES_DB` — database name
         - `POSTGRES_USER` — username. When using your own database, you must ensure that the user has the following rights: **Superuser**, **Create role**, **Create DB**, **Replication**, **Bypass RLS**.