diff --git a/docs/rules/a11y-no-visually-hidden-interactive-element.md b/docs/rules/a11y-no-visually-hidden-interactive-element.md
index 24af1e8b..52fdbc12 100644
--- a/docs/rules/a11y-no-visually-hidden-interactive-element.md
+++ b/docs/rules/a11y-no-visually-hidden-interactive-element.md
@@ -12,7 +12,7 @@ Note: we are not guarding against visually hidden `input` elements at this time.
 
 ### Why do we visually hide content?
 
-Visually hiding content can be useful when you want to provide information specifically to screen reader users or other assitive technology users while keeping content hidden from sighted users.
+Visually hiding content can be useful when you want to provide information specifically to screen reader users or other assistive technology users while keeping content hidden from sighted users.
 
 Applying the following css will visually hide content while still making it accessible to screen reader users.
 
@@ -61,7 +61,6 @@ width: 1px;
 
 - className - A css className that visually hides content. Defaults to `sr-only`.
 - componentName - A react component name that visually hides content. Defaults to `VisuallyHidden`.
-- htmlPropName - A prop name used to replace the semantic element that is rendered. Defaults to `as`.
 
 ```json
 {
@@ -69,8 +68,7 @@ width: 1px;
     "error",
     {
       "className": "visually-hidden",
-      "componentName": "VisuallyHidden",
-      "htmlPropName": "as"
+      "componentName": "VisuallyHidden"
     }
   ]
 }
diff --git a/lib/rules/a11y-no-visually-hidden-interactive-element.js b/lib/rules/a11y-no-visually-hidden-interactive-element.js
index ac3e7142..70f7c3cd 100644
--- a/lib/rules/a11y-no-visually-hidden-interactive-element.js
+++ b/lib/rules/a11y-no-visually-hidden-interactive-element.js
@@ -8,7 +8,6 @@ const defaultcomponentName = 'VisuallyHidden'
 const schema = generateObjSchema({
   className: {type: 'string'},
   componentName: {type: 'string'},
-  htmlPropName: {type: 'string'},
 })
 
 /** Note: we are not including input elements at this time