Merge pull request #204681 from JackStromberg/patch-74

Updating 303 verbiage

Author: PRMerger10

articles/application-gateway/redirect-overview.md

@@ -19,8 +19,8 @@ A common redirection scenario for many web applications is to support automatic
 A redirect type sets the response status code for the clients to understand the purpose of the redirect. The following types of redirection are supported:
 
 - 301 (Moved permanently): Indicates that the target resource has been assigned a new permanent URI. Any future references to this resource will use one of the enclosed URIs. Use 301 status code for HTTP to HTTPS redirection.
-- 303 (Permanent redirect): Indicates that the target resource has been assigned a new permanent URI. Any future references to this resource should use one of the enclosed URIs.
 - 302 (Found): Indicates that the target resource is temporarily under a different URI. Since the redirection can change on occasion, the client should continue to use the effective request URI for future requests.
+- 303 (See Other): Indicates that the target resource is redirecting the user agent to a different resource, as indicated by a URI in the Location header field.
 - 307 (Temporary redirect): Indicates that the target resource is temporarily under a different URI. The user agent MUST NOT change the request method if it does an automatic redirection to that URI. Since the redirection can change over time, the client ought to continue using the original effective request URI for future requests.
 
 ## Redirection capabilities