[Mlir-commits] [mlir] a5ae34a - [mlir][linalg] fixed typo

[Aart Bik]

Author: Aart Bik
Date: 2021-08-11T11:59:15-07:00
New Revision: a5ae34afaa457b546c592c93e9e5ead5276c3575

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

LOG: [mlir][linalg] fixed typo

Differential Revision: https://reviews.llvm.org/D107915

Added: 
    

Modified: 
    mlir/docs/Rationale/RationaleLinalgDialect.md

Removed: 
    


################################################################################
diff  --git a/mlir/docs/Rationale/RationaleLinalgDialect.md b/mlir/docs/Rationale/RationaleLinalgDialect.md
index c8dca244a4cb4..c0e351941b85c 100644
--- a/mlir/docs/Rationale/RationaleLinalgDialect.md
+++ b/mlir/docs/Rationale/RationaleLinalgDialect.md
@@ -547,7 +547,7 @@ data types. We choose to take advantage of these properties for the
 reasons described above.
 In particular, the `MemRefType` represents dense non-contiguous memory regions.
 This structure should extend beyond simple dense data types and generalize to
-ragged, sparse and mixed dens/sparse tensors as well as to trees, hash tables,
+ragged, sparse and mixed dense/sparse tensors as well as to trees, hash tables,
 tables of records and maybe even graphs.
 
 For such more advanced data types, the control-flow required to traverse the