diff --git a/content/en/xlt/load-testing/Advanced/060-cloud-setup.md b/content/en/xlt/load-testing/Advanced/060-cloud-setup.md
index 3550de88..c2bbac54 100644
--- a/content/en/xlt/load-testing/Advanced/060-cloud-setup.md
+++ b/content/en/xlt/load-testing/Advanced/060-cloud-setup.md
@@ -24,19 +24,30 @@ Distributed Load Generation Environment
 
 One machine runs your [master controller]({{< relref "../manual/010-basics#mcmaster-controller" >}}), which controls several machines that run the [agent controllers]({{< relref "../manual/010-basics#acagent-controller" >}}) and [agents]({{< relref "../manual/010-basics#agents" >}}). 
 
-Xceptance offers public images for AWS machines (AMIs). You can also use [XLT Packer](https://github.com/Xceptance/XLT-Packer) to build your own images for GCP and AWS. 
+#### XLT Images 
 
-XLT ships with two small scripts that simplify the process of setting up and managing load test instances: **[gce_admin]({{< relref "#google-cloud-gc" >}})** (for Google Cloud) and **[ec2_admin]({{< relref "#amazon-web-services-aws" >}})** (for Amazon Web Services).
+Xceptance provides ready-to-use **public XLT images** for AWS machines (AMIs) and Docker. These images are based on Debian, include the latest XLT and JDK (see release notes for current version info) and are tuned for load testing. For real browser load testing, they also include the latest Chromium and Firefox (ESR) browsers with matching web driver binaries, `chromedriver` and `geckodriver`.
 
-#### Add Machines to the MC Configuration
+If you are looking for XLT images for other clouds or just want to build your own image, visit XLT's sister project, **[XLT Packer](https://github.com/Xceptance/XLT-Packer/)**. This project not only contains scripts to install and set up the contents of an XLT image, but also provides Packer templates to actually create such images for the following clouds:
 
-The scripts will set up a cluster of test machines quickly. After the setup, you just have to add the machines to the master controller configuration: navigate to `<XLT>/config/mastercontroller.properties` on your MC machine, then enter the AC data the tools give you when you list the created instances. Now you are ready for load testing.
+* AWS
+* DigitalOcean
+* Google
+* Hetzner
+
+Follow the instructions in the project's README file to create an XLT image for one of the supported clouds yourself.
+
+#### Setting Up and Managing Load Test Instances
+
+XLT ships with two small scripts that simplify the process of **setting up** and **managing** load test instances: **[gce_admin]({{< relref "#google-cloud-gc" >}})** (for Google Cloud) and **[ec2_admin]({{< relref "#amazon-web-services-aws" >}})** (for Amazon Web Services).
+
+The scripts will set up a cluster of test machines quickly. After the setup, you just have to **add the machines to the master controller configuration**: navigate to `<XLT>/config/mastercontroller.properties` on your MC machine, then enter the AC data the tools give you when you list the created instances. Now you are ready for load testing.
 
 {{% note title="How many machines do I need?" %}}
 It can be hard to determine the number and size of load testing machines you'll need for your setup. Here's [a small guide about test sizing]({{< relref "../how-tos/test-sizing" >}}).
 {{% /note %}}
 
-After your test finished and the mastercontroller has downloaded all the data required for report generation, gce_admin/ec2_admin can also help you to easily terminate all of your test machines.
+After your test finished and the mastercontroller has downloaded all the data required for report generation, gce_admin/ec2_admin can also help you to easily **terminate** all of your test machines.
 
 ## Google Cloud (GCP)
 
diff --git a/content/en/xlt/load-testing/Manual/530-reports.md b/content/en/xlt/load-testing/Manual/530-reports.md
index d39c8743..305e8847 100644
--- a/content/en/xlt/load-testing/Manual/530-reports.md
+++ b/content/en/xlt/load-testing/Manual/530-reports.md
@@ -45,12 +45,12 @@ Every section of the comparison report displays a table with performance changes
 
 When you hover the mouse over the columns of the report table, you can see the actual measurement results, which let you determine whether or not the reported percentage change is significant.
 
-{{< image src="user-manual/comparison_report_1-small.png" large="user-manual/comparison_report_1.png" >}}
+{{< image max-width="60%" src="user-manual/comparison_report_1.png" >}}
 Performance Comparison Report - Overview
 {{< /image >}}
 
-{{< image src="user-manual/comparison_report_2-small.png" large="user-manual/comparison_report_2.png" >}}
-Performance Comparison Report
+{{< image max-width="60%" src="user-manual/comparison_report_2.png" >}}
+Performance Comparison Report - Actions
 {{< /image >}}
 
 ### Sections
diff --git a/static/images/user-manual/comparison_report_1-small.png b/static/images/user-manual/comparison_report_1-small.png
deleted file mode 100644
index f5c92137..00000000
Binary files a/static/images/user-manual/comparison_report_1-small.png and /dev/null differ
diff --git a/static/images/user-manual/comparison_report_1.png b/static/images/user-manual/comparison_report_1.png
index 373b59d1..6793da9e 100644
Binary files a/static/images/user-manual/comparison_report_1.png and b/static/images/user-manual/comparison_report_1.png differ
diff --git a/static/images/user-manual/comparison_report_2-small.png b/static/images/user-manual/comparison_report_2-small.png
deleted file mode 100644
index a5331774..00000000
Binary files a/static/images/user-manual/comparison_report_2-small.png and /dev/null differ
diff --git a/static/images/user-manual/comparison_report_2.png b/static/images/user-manual/comparison_report_2.png
index f0e5cf92..eeab0085 100644
Binary files a/static/images/user-manual/comparison_report_2.png and b/static/images/user-manual/comparison_report_2.png differ