[llvm] dbe5613 - [llvm][docs] Fix text rendering in external suites section of Test suite guide

[David Spickett via llvm-commits]

Author: David Spickett
Date: 2025-05-09T13:11:17Z
New Revision: dbe561309a1cb35e11cc57e4b88096362a030e8a

URL: https://github.com/llvm/llvm-project/commit/dbe561309a1cb35e11cc57e4b88096362a030e8a
DIFF: https://github.com/llvm/llvm-project/commit/dbe561309a1cb35e11cc57e4b88096362a030e8a.diff

LOG: [llvm][docs] Fix text rendering in external suites section of Test suite guide

Since the "-" was the first character of a newline, it was rendered
as a bullet point when it was supposed to be punctuation.

Added: 
    

Modified: 
    llvm/docs/TestSuiteGuide.md

Removed: 
    


################################################################################
diff  --git a/llvm/docs/TestSuiteGuide.md b/llvm/docs/TestSuiteGuide.md
index 1bb015218b08d..8a64e756d0737 100644
--- a/llvm/docs/TestSuiteGuide.md
+++ b/llvm/docs/TestSuiteGuide.md
@@ -377,8 +377,8 @@ The `train` dataset is used by default.
 
 In addition to SPEC, the multimedia frameworks ffmpeg and dav1d can also
 be hooked up as external projects in the same way. By including them in
-llvm-test-suite, a lot more of potentially vectorizable code gets compiled
-- which can catch compiler bugs merely by triggering code generation asserts.
+llvm-test-suite, a lot more of potentially vectorizable code gets compiled -
+which can catch compiler bugs merely by triggering code generation asserts.
 Including them also adds small code correctness tests, that compare the
 output of the compiler generated functions against handwritten assembly
 functions. (On x86, building the assembly requires having the nasm tool