From dce87c7e1908d9d25178371c6db75681f4384110 Mon Sep 17 00:00:00 2001
From: Sujit Mohanty <91360351+sujitmohanty@users.noreply.github.com>
Date: Mon, 16 Dec 2024 00:56:53 +0100
Subject: [PATCH] Fix typo in "super" keyword reference page (#37221)

Changed "seeked" to "sought"
---
 files/en-us/web/javascript/reference/operators/super/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/files/en-us/web/javascript/reference/operators/super/index.md b/files/en-us/web/javascript/reference/operators/super/index.md
index 159ee8c0c005211..0ef3164e56ab153 100644
--- a/files/en-us/web/javascript/reference/operators/super/index.md
+++ b/files/en-us/web/javascript/reference/operators/super/index.md
@@ -175,7 +175,7 @@ obj2.method2(); // Logs "method 1"
 
 ### Methods that read super.prop do not behave differently when bound to other objects
 
-Accessing `super.x` behaves like `Reflect.get(Object.getPrototypeOf(objectLiteral), "x", this)`, which means the property is always seeked on the object literal/class declaration's prototype, and unbinding and re-binding a method won't change the reference of `super`.
+Accessing `super.x` behaves like `Reflect.get(Object.getPrototypeOf(objectLiteral), "x", this)`, which means the property is always sought on the object literal/class declaration's prototype, and unbinding and re-binding a method won't change the reference of `super`.
 
 ```js
 class Base {