From afed314e33bc1bf1c0abe54338a8f6a1aa6e17a8 Mon Sep 17 00:00:00 2001
From: chinmay7016 <75988613+chinmay7016@users.noreply.github.com>
Date: Tue, 31 Oct 2023 03:54:53 +0530
Subject: [PATCH] Update endpoint.md (#475)

fixed the typo error
---
 crates/oapi/docs/endpoint.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/crates/oapi/docs/endpoint.md b/crates/oapi/docs/endpoint.md
index 7dd5e609c..15803105b 100644
--- a/crates/oapi/docs/endpoint.md
+++ b/crates/oapi/docs/endpoint.md
@@ -5,7 +5,7 @@ Macro accepts set of attributes that can be used to configure and override defau
 You can use the Rust's own `#[deprecated]` attribute on functions to mark it as deprecated and it will
 reflect to the generated OpenAPI spec. Only **parameters** has a special **deprecated** attribute to define them as deprecated.
 
-`#[deprecated]` attribute supports adding additional details such as a reason and or since version but this is is not supported in
+`#[deprecated]` attribute supports adding additional details such as a reason and or since version but this is not supported in
 OpenAPI. OpenAPI has only a boolean flag to determine deprecation. While it is totally okay to declare deprecated with reason
 `#[deprecated  = "There is better way to do this"]` the reason would not render in OpenAPI spec.