diff --git a/knowledge-base/images/CheckStubsPrintPreview.png b/knowledge-base/images/CheckStubsPrintPreview.png
new file mode 100644
index 000000000..168c9d447
Binary files /dev/null and b/knowledge-base/images/CheckStubsPrintPreview.png differ
diff --git a/knowledge-base/two-lists-show-details-in-parallel.md b/knowledge-base/two-lists-show-details-in-parallel.md
index 052c0cdb1..4f84a6fca 100644
--- a/knowledge-base/two-lists-show-details-in-parallel.md
+++ b/knowledge-base/two-lists-show-details-in-parallel.md
@@ -1,6 +1,6 @@
 ---
-title: Report with Two Lists Showing the Same Data in Parallel Page by Page
-description: "Learn how to create a report that shows the same data twice per page in parallel in Telerik Reporting."
+title: Check with Stubs. Report with Two Lists Showing the Same Data in Parallel Page by Page
+description: "Learn how to create a report that shows the same data twice per page in parallel in Telerik Reporting. The approach is relevant for printing checks with stubs."
 type: how-to
 page_title: Two Lists Showing the Same Data in Parallel
 slug: two-lists-show-details-in-parallel
@@ -27,7 +27,9 @@ The purpose of the report we are going to create is to list a number of _checks_
 1. Each _check_ should start on a new page and its main/header information should be printed only on the page header of the first page associated with this _check_. The rest of the pages related to the _check_ must contain static text in the page header, for example, 'Void'.
 1. The _stubs_ for the _check_ should be printed twice in parallel. The idea is for the printed reports to allow these two sections with the _check stubs_ to be easily cut, one going to the payees for their records.
 
-The report layout consists of three parts. The top part contains the main information about the _check_, or the static text ('Void') in a header. The middle and bottom parts would represent the two identical (or different, depending on the scenario, but representing the same data rows) _check stubs_.
+The report layout consists of three parts. The top part contains the main information about the _check_, or the static text ('Void') in a header. The middle and bottom parts would represent the two identical (or different, depending on the scenario, but representing the same data rows) _check stubs_. Here is how our final report will look in the PrintPreview mode of the Standalone Report Designer:
+
+![The first and second page of the Check Stubs sample report 'TwoParallelLists.trdx' in PrintPreview of the Standalone Report Designer](images/CheckStubsPrintPreview.png "Check Stubs Report PrintPreview")
 
 The main challenge here is that if there are more _stub_ lines within a single _check_ that cannot fit on a single page, we need to ensure: