From 0219a05d1e95777159dbb0ccf042bb6844cfc2f6 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Mon, 1 Jan 2024 22:38:20 -0500
Subject: [PATCH] spelling: notable

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
 docs/src/index.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/index.rst b/docs/src/index.rst
index 207238f37..9f0445a18 100644
--- a/docs/src/index.rst
+++ b/docs/src/index.rst
@@ -19,7 +19,7 @@ The main differences between MLX and NumPy are:
 
 The design of MLX is inspired by frameworks like `PyTorch
 <https://pytorch.org/>`_, `Jax <https://github.com/google/jax>`_, and
-`ArrayFire <https://arrayfire.org/>`_. A noteable difference from these
+`ArrayFire <https://arrayfire.org/>`_. A notable difference from these
 frameworks and MLX is the *unified memory model*. Arrays in MLX live in shared
 memory. Operations on MLX arrays can be performed on any of the supported
 device types without performing data copies. Currently supported device types