Use literal blocks for console I/O to separate it from the
surrounding text. Otherwise the lines run together, without any
clear break before or after the commands.

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
Cc: Jithu Joseph <jithu.joseph@intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Ashok Raj <ashok.raj.linux@gmail.com>
Cc: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Cc: platform-driver-x86@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org

 Documentation/ABI/testing/sysfs-platform-intel-ifs |    6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

--- linux-next-20260918.orig/Documentation/ABI/testing/sysfs-platform-intel-ifs
+++ linux-next-20260918/Documentation/ABI/testing/sysfs-platform-intel-ifs
@@ -10,8 +10,10 @@ Description:	Write <cpu#> to trigger IFS
 		Note that the test is per core. The cpu# can be
 		for any thread on the core. Running on one thread
 		completes the test for the core containing that thread.
-		Example: to test the core containing cpu5: echo 5 >
-		/sys/devices/virtual/misc/intel_ifs_<N>/run_test
+		Example: to test the core containing cpu5::
+
+		  echo 5 > /sys/devices/virtual/misc/intel_ifs_<N>/run_test
+
 Devices:	all
 
 What:		/sys/devices/virtual/misc/intel_ifs_<N>/status