From 0f30ae5e27b1451ff216492e972a3a60321acd55 Mon Sep 17 00:00:00 2001
From: Junseo Yoo <59751754+joonyoo181@users.noreply.github.com>
Date: Thu, 30 May 2024 15:58:44 -0700
Subject: [PATCH] Update index-type-operator.md

Nitpick on the title of the RFC
---
 docs/index-type-operator.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/index-type-operator.md b/docs/index-type-operator.md
index 3bcde82..51880d5 100644
--- a/docs/index-type-operator.md
+++ b/docs/index-type-operator.md
@@ -1,4 +1,4 @@
-# `index` type operators
+# `index` type operator
 
 ## Summary
 
@@ -74,4 +74,4 @@ A drawback to this feature is the possible increase in cost of maintenance. In t
 
 ## Alternatives
 
-An alternative to the proposed implementation is utilizing inexact table types and exact table types (to be implemented) to handle the edge in a simpler manner. If we know that the indexee is an inexact table type, the index type operator can return the `unknown` type. If we know that the indexee is an exact table type, we can return an error.
\ No newline at end of file
+An alternative to the proposed implementation is utilizing inexact table types and exact table types (to be implemented) to handle the edge in a simpler manner. If we know that the indexee is an inexact table type, the index type operator can return the `unknown` type. If we know that the indexee is an exact table type, we can return an error.