diff --git a/packages/docs/docs/concepts/cornerstone-core/imageLoader.md b/packages/docs/docs/concepts/cornerstone-core/imageLoader.md
index e5a7fba730..0ff2c1d467 100644
--- a/packages/docs/docs/concepts/cornerstone-core/imageLoader.md
+++ b/packages/docs/docs/concepts/cornerstone-core/imageLoader.md
@@ -15,7 +15,7 @@ an [`Image Object`](./images.md). Since loading images usually requires a call t
 1. `ImageLoaders` register themselves using [`registerImageLoader`](/api/core/namespace/imageLoader#registerImageLoader) API with cornerstone to load specific ImageId URL schemes
 2. The application requests to load an image using the `loadImage` API for stack or `createAndCacheVolume` API for volume.
 3. Cornerstone delegates the request to load the image to the `ImageLoader` registered with the URL scheme of the imageId.
-4. The ImageLoader will return an `Image Load Object` containing a Promise which it will resolve with the corresponding Image Object once it has obtained the pixel data. Obtaining the pixel data may may require a call to a remote server using `XMLHttpRequest`, decompression of the pixel data (e.g. from JPEG 2000), and conversion of the pixel data into the format that Cornerstone understands (e.g. RGB vs YBR color).
+4. The ImageLoader will return an `Image Load Object` containing a Promise which it will resolve with the corresponding Image Object once it has obtained the pixel data. Obtaining the pixel data may require a call to a remote server using `XMLHttpRequest`, decompression of the pixel data (e.g. from JPEG 2000), and conversion of the pixel data into the format that Cornerstone understands (e.g. RGB vs YBR color).
 5. The [Image Object](./images.md) passed back by the resolved Promise is then displayed using `renderingEngine` API.
 
 ## Register Image Loader