Update schedule-antivirus-scan-anacron.md

Author: denisebmsft

defender-endpoint/schedule-antivirus-scan-anacron.md

@@ -47,12 +47,14 @@ But if the Linux devices are shut down or offline during the cron schedule, scan
 Use the following steps to schedule scans:
 
 1. Connect to the RedHat server using PuTTY.
-1. Edit the anacron file:
+
+2. Edit the anacron file as follows:
+
    ```shell
    vi /etc/anacron
    ```
 
-1.  :::image type="content" source="media/vi-etc-anacron.png" alt-text="Sample Anacron Job Linux." lightbox="media/vi-etc-anacron.png" link="media/vi-etc-anacron.png":::
+3. Review and edit your Anacron file, which contains the following information:
 
    ```shell
    # /etc/anacrontab: configuration file for anacron
@@ -65,19 +67,24 @@ Use the following steps to schedule scans:
    # delay will be 5 minutes + RANDOM_DELAY for cron.daily
    ```
 
-1. Note the following items in the file.
-   1. **Shell:** Shell is referred as `/bin/sh`, and not as `/bin/bash`. Remember when writing the jobs.
-   1. **RANDOM_DELAY:** Describes the maximum time in minutes for the job. This value is used to offset the jobs so there wouldn't be too many jobs running at the same time. Using this delay is ideal for VDI solutions.
-   1. **START_HOURS_RANGE:** Describes the time range to run the job.
-   1. **cron.daily:** Describes 1 as the period of days required for the frequency of job executions. 5 is the delay in minutes that anacron waits after the device restarts.
+   Notice the following items in the file:
+
+   - **Shell** is referred as `/bin/sh`, and not as `/bin/bash`. Remember this when you're configuring jobs.
+   - **RANDOM_DELAY** describes the maximum time in minutes for the job. This value is used to offset the jobs so there aren't be too many jobs running at the same time. Using this delay is ideal for VDI solutions.
+   - **START_HOURS_RANGE** describes the time range to run the job.
+   - **cron.daily** describes `1` as the period of days required for the frequency of job executions. `5 is the delay in minutes that anacron waits after the device restarts.
 
-1. Review look at the anacron jobs:
+4. Review your anacron jobs by using the following command:
 
    ```shell
    ls -lh /etc/cron*
    ```
 
-    :::image type="content" source="media/vi-etc-anacron.png" alt-text="Sample Anacron Job Linux." lightbox="media/vi-etc-anacron.png" link="media/vi-etc-anacron.png":::
+   You should see information similar to what's shown in the following screenshot:
+
+   :::image type="content" source="media/vi-etc-anacron.png" alt-text="Sample Anacron Job Linux." lightbox="media/vi-etc-anacron.png" link="media/vi-etc-anacron.png":::
+
+   The following code example provides a more detailed view:
 
    ```shell
    [root@redhat7 /] # ls -lh /etc/cron*
@@ -116,9 +123,9 @@ Use the following steps to schedule scans:
    total 0
    ```
 
-1. Ignore the `/etc/cron.d` directory, you will see `/etc/cron.daily, hourly, monthly, and weekly`.
+   Ignore the `/etc/cron.d` directory; instead, review `/etc/cron.daily, hourly, monthly, and weekly`.
 
-1. To schedule a weekly antivirus scan, you can create a file (Job) under the ```/etc/cron.weekly``` directory.
+5. To schedule a weekly antivirus scan, you can create a file (Job) under the ```/etc/cron.weekly``` directory.
 
    ```shell
    cd /etc/cron.weekly
@@ -144,7 +151,7 @@ Use the following steps to schedule scans:
    Type: wq!
    ```
 
-1. Change the file permissions to allow the file to be executed.
+6. Change the file permissions to allow the file to be executed by using this command: 
 
    ```shell
    Chmod 755 mdavfullscan
@@ -167,13 +174,13 @@ Use the following steps to schedule scans:
    [root@redhat7 cron.weekly] #
    ```
 
-1. Use the command to test the weekly anacron job.
+7. Use the following command to test the weekly anacron job:
 
    ```shell
    ./mdavfullscan
    ```
 
-1. Use the command to verify the job ran successfully.
+8. Use the following command to verify the job ran successfully:
 
    ```shell
    cat /logs/mdav_avacron_full_scan.log