Use backticks consistently

Author: erichaagdev

components/scripts/gradle/01-validate-incremental-building.sh

@@ -299,47 +299,20 @@ EOF
   wait_for_enter
 }
 
-explain_and_print_summary() {
-  read_build_scan_metadata
-  local text
-  IFS='' read -r -d '' text <<EOF
-The 'Summary' section below captures the configuration of the experiment and the
-two build scans that were published as part of running the experiment. The build
-scan of the second build is particularly interesting since this is where you can
-inspect what tasks were not leveraging Gradle’s incremental build functionality.
-
-The 'Investigation Quick Links' section below allows quick navigation to the
-most relevant views in build scans to investigate what tasks were uptodate and
-what tasks executed in the second build, which of those tasks had the biggest
-impact on build performance, and what caused those tasks to not be uptodate.
-
-$(explain_performance_characteristics)
-
-$(explain_command_to_repeat_experiment)
-
-$(print_summary)
-
-$(print_command_to_repeat_experiment)
-
-$(explain_when_to_rerun_experiment)
-EOF
-  print_wizard_text "${text}"
-}
-
 explain_and_print_summary() {
   read_build_scan_metadata
   local text
   if [[ "${build_scan_publishing_mode}" == "on" ]]; then
     IFS='' read -r -d '' text <<EOF
-The 'Summary' section below captures the configuration of the experiment and
+The ‘Summary’ section below captures the configuration of the experiment and
 the two build scans that were published as part of running the experiment. The
 build scan of the second build is particularly interesting since this is where
 you can inspect what tasks were not leveraging Gradle’s incremental build
 functionality.
 
 $(explain_performance_characteristics)
 
-The 'Investigation Quick Links' section below allows quick navigation to the
+The ‘Investigation Quick Links’ section below allows quick navigation to the
 most relevant views in build scans to investigate what tasks were up-to-date
 and what tasks executed in the second build, which of those tasks had the
 biggest impact on build performance, and what caused those tasks to not be