From c28b9ce8a8a600c557e09d08a93038d3f513b246 Mon Sep 17 00:00:00 2001 From: Dmytro Doroshenko <855874+TrickyCat@users.noreply.github.com> Date: Sat, 19 Apr 2025 11:55:06 +0300 Subject: [PATCH] Fix a typo --- docs/high-performance/Memory2D.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/high-performance/Memory2D.md b/docs/high-performance/Memory2D.md index 6d44f4a87..2a237c3aa 100644 --- a/docs/high-performance/Memory2D.md +++ b/docs/high-performance/Memory2D.md @@ -40,7 +40,7 @@ This configuration allows `Memory2D` to be extremely flexible in the way it m - A 2D `T[,]` array, mapped directly to a `Memory2D` instance. - A 3D `T[,,]` array, with a `Memory2D` instance representing a given depth slice (a layer). -The `Memory` type also exposes a number of utility methods, including most of the same API surface that the standard `Memory` implements. For instance, it includes a `Slice(int, int)` method that makes it easy to do 2D slicing operations directly on the virtual 2D memory location, with the `Memory2D` instance automatically adjusting the necessary parameters internally to shift its mapping on the right memory area(s) corresponding to the requested result. +The `Memory2D` type also exposes a number of utility methods, including most of the same API surface that the standard `Memory` implements. For instance, it includes a `Slice(int, int)` method that makes it easy to do 2D slicing operations directly on the virtual 2D memory location, with the `Memory2D` instance automatically adjusting the necessary parameters internally to shift its mapping on the right memory area(s) corresponding to the requested result. ## Syntax