[Mlir-commits] [mlir] Fix MLIR Transform Tutorial Doc (PR #155285)

[Brandon Kirincich]

https://github.com/BrandonKi created https://github.com/llvm/llvm-project/pull/155285

Fixes a small issue I noticed while reading through the tutorial.

>From 07445a857a259ea68fee826acc893ca1b5cd1af8 Mon Sep 17 00:00:00 2001
From: Brandon Kirincich <44515121+BrandonKi at users.noreply.github.com>
Date: Mon, 25 Aug 2025 16:08:59 -0400
Subject: [PATCH] Fix MLIR Transform Tutorial Doc

---
 mlir/docs/Tutorials/transform/Ch0.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mlir/docs/Tutorials/transform/Ch0.md b/mlir/docs/Tutorials/transform/Ch0.md
index dc4b753f98caa..0d7a70364742d 100644
--- a/mlir/docs/Tutorials/transform/Ch0.md
+++ b/mlir/docs/Tutorials/transform/Ch0.md
@@ -134,7 +134,7 @@ Furthermore, the operation now contains a region that explicitly specifies the m
 
 ## “Loop” Fusion
 
-Since the region of the `linalg.generic` operation can contain arbitrarily many operations, we can use it to express “fusion” of the implicit loops by simply having more operations chained in the region. For example, the common machine learning rectified linear unit layer (ReLU), which can be defined as `relu(x) = max(0, x)`, can be defined be expressed using the “compare-and-select” idiom in one `linalg.generic` operation, without the temporary buffer for the comparison result and without repeating the outer operation:
+Since the region of the `linalg.generic` operation can contain arbitrarily many operations, we can use it to express “fusion” of the implicit loops by simply having more operations chained in the region. For example, the common machine learning rectified linear unit layer (ReLU), which can be defined as `relu(x) = max(0, x)`, can be expressed using the “compare-and-select” idiom in one `linalg.generic` operation, without the temporary buffer for the comparison result and without repeating the outer operation:
 
 ```mlir
 linalg.generic {