[Mlir-commits] [mlir] f763270 - [mlir] Replace HTML escaped character

[llvmlistbot at llvm.org]

Author: Kai Sasaki
Date: 2023-06-24T02:43:40Z
New Revision: f763270b5315bb74cf6fa79c8f39d4f6633a29d3

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

LOG: [mlir] Replace HTML escaped character

Added: 
    

Modified: 
    mlir/docs/Tutorials/transform/Ch1.md

Removed: 
    


################################################################################
diff  --git a/mlir/docs/Tutorials/transform/Ch1.md b/mlir/docs/Tutorials/transform/Ch1.md
index 3db39312ebb13..021e0ea4d128e 100644
--- a/mlir/docs/Tutorials/transform/Ch1.md
+++ b/mlir/docs/Tutorials/transform/Ch1.md
@@ -51,7 +51,7 @@ The first entry block argument is mandatory for top-level transform operations a
 
 The remaining entry block arguments are optional and can be associated with payload attributes, operations or values that are useful in the sequence. These are also specified when calling `applyTransforms`. In our case, we are interested in the matrix multiplication and elementwise operations that we are going to tile and fuse.
 
-All value handles have Transform dialect types. These types specify certain properties of the payload IR entities associated with them. In this example, `transform.any_op` indicates that the handle is associated with arbitrary payload operations. On the contrary, `transform.op<"X">` indicates that the handle is associated _only_ with payload operations of kind `X`. These constraints are verified when the handle/payload association is created. For entry block arguments of top-level transform operations, this happens early in the `applyTransforms` function. If the constraints are not satisfied, the transform application fails and produces diagnostics for the user.
+All value handles have Transform dialect types. These types specify certain properties of the payload IR entities associated with them. In this example, `transform.any_op` indicates that the handle is associated with arbitrary payload operations. On the contrary, `transform.op<"X">` indicates that the handle is associated _only_ with payload operations of kind `X`. These constraints are verified when the handle/payload association is created. For entry block arguments of top-level transform operations, this happens early in the `applyTransforms` function. If the constraints are not satisfied, the transform application fails and produces diagnostics for the user.
 
 ## Failure Propagation