Update documentation wording

Author: krzysz00

mlir/include/mlir/Dialect/AMDGPU/IR/AMDGPU.td

@@ -186,7 +186,7 @@ def AMDGPU_FatRawBufferCastOp :
     If `validBytes` is given, it is the number of bytes that will be valid as
     an offset to `out`. If it is not provided, this will be inferred from
     the size of the memref during lowering. This size is
-    max_d (sizes[d] * strides[d]) * sizeof(element type)..
+    max_{d = 0 upto rank(source)} (sizes[d] * strides[d]) * sizeof(element type).
 
     The flags of the buffer descriptor will be set up to enable raw usage -
     for example, stride = 0, add_tid = 0, and so on. The `boundsCheck`

mlir/include/mlir/Dialect/AMDGPU/Transforms/Passes.td

@@ -37,9 +37,13 @@ def AmdgpuResolveStridedMetadataPass : Pass<"amdgpu-resolve-strided-metadata"> {
     This pass rrewrites `memref.extract_strided_metadata` operations
     targeting the AMDGPU dialect casts.
 
-    It's mainly meant for testing - please incorporate the patterns into your
-    own extract-strided-metadata passes (or run memref's expand-strided-metadata
-    again after this).
+    The patterns in this pass should normally be run alongside those in
+    -expand-strided-metadata, and creating a pass that combines those two
+    sets of patterns is the recommended way to use this functionality.
+    However, this pass (which will likely need a second -expand-strided-metadata
+    after it) is provided so that simple usecases do not need to create custom passes.
+    These patterns have not been added to -expnad-strided-metadata to
+    prevent the memref dialect from depending on platform-specific code.
   }];
   let dependentDialects = [
     "arith::ArithDialect",