From d9c656db2e81c8bda2f44e560ffbd4f7d1ceae27 Mon Sep 17 00:00:00 2001 From: vyanovsky <51786050+vyanovsky@users.noreply.github.com> Date: Tue, 4 Jul 2023 16:40:14 +0300 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Helen <58733007+el-termikael@users.noreply.github.com> --- docs/adguard-for-android/solving-problems/logcat.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/adguard-for-android/solving-problems/logcat.md b/docs/adguard-for-android/solving-problems/logcat.md index bc9c266488c..254389d21a4 100644 --- a/docs/adguard-for-android/solving-problems/logcat.md +++ b/docs/adguard-for-android/solving-problems/logcat.md @@ -9,7 +9,7 @@ This article covers AdGuard for Android, a multifunctional ad blocker that prote ::: -Sometimes a regular log may not be enough to identify the origin of the problem. In such cases a system log is needed. Below is the instruction how to collect and get it: via Developer options and Logcat. +Sometimes a regular log may not be sufficient to identify the origin of the problem. In such cases a system log is needed. Below are instructions on how to collect and get it: via Developer options and Logcat. ## Capture a bug report from a device @@ -88,7 +88,7 @@ An example of a successful result: `adb logcat -v threadtime -d > C:\Program Files\platform-tools\logs.txt` -Email the created `txt` file as well as problem reproduction time (from part #2) to our support team at support@adguard.com. +Email the created `txt` file as well as the time the problem was reproduced (from part #2) to our support team at support@adguard.com. ### Alternative way for ROOT users: