Merge branch 'ag-49212-add-article-TDI-Chrome-142' of https://github.com/AdguardTeam/KnowledgeBase into ag-49212-add-article-TDI-Chrome-142

Author: puglieri

docs/adguard-for-windows/solving-problems/tdi-driver-and-Chrome-142.md

@@ -60,7 +60,7 @@ You can apply the necessary registry changes automatically by using one of the p
 
 If your browser is not listed, follow the manual instructions below to create the necessary registry entries:
 
-1. Determine its policy branch by checking the vendor’s official documentation, or opening the internal policy page. On Chrome, navigate to `chrome://policy`. Other browsers use a similar path.
+1. Determine its policy branch by checking the vendor’s official documentation or by opening the internal policy page. In Chrome, navigate to `chrome://policy`. Other browsers use a similar path.
 
 1. Identify the correct registry branch for your browser. Different Chromium-based browsers use different policy paths under `HKLM`. It should follow the model `HKLM\SOFTWARE\Policies\<Vendor>\<Product>`.
 
@@ -92,7 +92,7 @@ Repeat the same logic for Chromium, Edge, Brave, Vivaldi, Yandex Browser, etc. Y
 
 1. Add the required registry values:
 
-    - In the correct key, click the right panel → *New → DWORD (32-bit) Value*
+    - In the correct key, click the right panel → *New* → *DWORD (32-bit) Value*
     - Name it `RendererAppContainerEnabled`
 
     - Double-click it and set: