From 7f8b9aa520340352d73d874d1c1b3abac26f9068 Mon Sep 17 00:00:00 2001
From: Nathan Coleman <nathandanielcoleman@gmail.com>
Date: Wed, 27 Apr 2022 14:14:27 -0400
Subject: [PATCH] Update
 website/content/docs/api-gateway/upgrade-specific-versions.mdx

Co-authored-by: Karl Cardenas <kcardenas@hashicorp.com>
---
 .../content/docs/api-gateway/upgrade-specific-versions.mdx    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/content/docs/api-gateway/upgrade-specific-versions.mdx b/website/content/docs/api-gateway/upgrade-specific-versions.mdx
index a2f836f6d..aac9b77fb 100644
--- a/website/content/docs/api-gateway/upgrade-specific-versions.mdx
+++ b/website/content/docs/api-gateway/upgrade-specific-versions.mdx
@@ -231,8 +231,8 @@ Ensure that the following requirements are met prior to upgrading:
 
 1. (Optional) Delete and recreate your routes. Note that it may take several minutes for attached routes to reconcile and start reporting bind errors.
   ```shell-session
-  $ kubectl delete -f <path_to_route_config.yaml>
-  $ kubectl create -f <path_to_route_config.yaml>
+  $ kubectl delete --filename <path_to_route_config.yaml>
+  $ kubectl create --filename <path_to_route_config.yaml>
   ```
 
 ## Post-Upgrade Configuration Changes