fix bullet list and replace screenshot

Author: nedaKaighobadi

docs/organizations/reporting/images/organization-overview-coverage.png

@@ -127,16 +127,23 @@ For calculation details, see [how code coverage is calculated](../../faq/code-an
 ### Coverage dashboard on Paid plans
 
 ![Image of the Coverage tab](./images/organization-overview-coverage.png)
-![Image of File Coverage section](./images/organization-overview-file-coverage.png)
 
 The Coverage tab on paid plans is divided into two main sections:
-- **Line coverage** that uses three main metrics:
+
+- **Line coverage**
+
+    Uses three main metrics:
+
     - **Covered lines**: Number of covered lines reported to Codacy.
     - **Coverable lines**: Number of lines that can be covered, based on coverage reports.
-    - **Coverage percentage**: The percentage of covered lines
-- **File coverage** that uses two main metrics:
-    - **Files with coverage**: Number of files that have coverage
-    - **Total files**: Total number of files
+    - **Coverage percentage**: The percentage of covered lines.
+
+- **File coverage**
+
+    Uses two main metrics:
+
+    - **Files with coverage**: Number of files that have coverage.
+    - **Total files**: Total number of files.
 
 These metrics drive all dashboard components:
 
@@ -145,9 +152,9 @@ These metrics drive all dashboard components:
 | **Coverage** | `coveredLines / coverableLines` <br/>Aggregation of all covered lines divided by all coverable lines across all repositories (or the current filter selection, see [filters](#overview-filters)). Includes only repositories reporting coverage. |
 | **Repositories reporting coverage** | Repositories with coverage data from the latest merged pull request. For example, if the latest merged pull request reported coverage metrics to Codacy, that repository is counted as reporting coverage. |
 | **Coverage trend** | Time-based trend for covered lines, uncovered lines, and organization coverage (or the current filter selection, see [filters](#overview-filters)). You can choose time ranges and granularity, and select a date to see which repositories changed the most during that period. |
-| **File coverage** | `filesWithCoverage/ totalFiles` Aggregation of all the files that have coverage divided by all the files across all repositories (or the current filter selection, see [filters](#overview-filters)). Includes only languages that support coverage. |
+| **File coverage** | `filesWithCoverage / totalFiles` <br/>Aggregation of all the files that have coverage divided by all the files across all repositories (or the current filter selection, see [filters](#overview-filters)). Includes only languages that support coverage. |
 | **Files by coverage percentage** | Distribution chart grouping the files with coverage into coverage ranges: very low, low, medium, high, and very high. You can select one or more ranges to see the distribution of selected ranges for each language in the languages chart, each day in the trend chart, and the number of files within that range for each repository. |
-| **File coverage by language** | Language breakdown showing file coverage percentages and covered/total file counts per language.You can choose one or more languages to view coverage performance across your repositories for those selected languages. |
+| **File coverage by language** | Language breakdown showing file coverage percentages and covered/total file counts per language. You can choose one or more languages to view coverage performance across your repositories for those selected languages. |
 | **File coverage trend** | Time-based trend for covered files, uncovered files, and overall file coverage percentage. You can choose time ranges and granularity, and select a date to see which repositories changed the most during that period. |
 
 You can export data from each chart using the ellipsis icon in the top-right corner in JSON or CSV format.