Update swagger.md

Author: kamilmysliwiec

content/recipes/swagger.md

@@ -158,7 +158,7 @@ With `isArray` set to **true**, the `enum` can be selected as a **multi-select**
 
 <figure><img src="/assets/enum_query_array.gif" /></figure>
 
-#### Enums Schema
+#### Enums schema
 
 By default, the `enum` property will add a raw definition of [Enum](https://swagger.io/docs/specification/data-models/enums/) on the `parameter`.
 
@@ -173,35 +173,18 @@ CatDetail:
           - Persian
           - Tabby
           - Siamese
-    ...
-    
-CatInformation:
-  type: 'object'
-  properties:
-    ...
-    - breed:
-        type: 'string'
-        enum:
-          - Persian
-          - Tabby
-          - Siamese
-    ...
 ```
 
 The above specification works fine for most cases. However, if you are utilizing a tool that takes the specification as **input** and generates **client-side** code, you might run into a problem with the generated code containing duplicated `enums`. Consider the following code snippet: 
 
 ```typescript
 // generated client-side code
 export class CatDetail {
-  ...
    breed: CatDetailEnum;
-   ...
 }
 
 export class CatInformation {
-  ...
   breed: CatInformationEnum;
-  ...
 }
 
 export enum CatDetailEnum {
@@ -224,17 +207,8 @@ To address this issue, you can pass an `enumName` next to `enum` property in you
 
 ```typescript
 export class CatDetail {
-  ...
    @ApiProperty({ enum: CatBreed, enumName: 'CatBreed' })
    breed: CatBreed;
-   ...
-}
-
-export class CatInformation {
-  ...
-   @ApiProperty({ enum: CatBreed, enumName: 'CatBreed' })
-   breed: CatBreed;
-   ...
 }
 ```
 
@@ -248,17 +222,6 @@ CatDetail:
     - breed:
         schema:
           $ref: '#/components/schemas/CatBreed'
-    ...
-    
-CatInformation:
-  type: 'object'
-  properties:
-    ...
-    - breed:
-        schema:
-          $ref: '#/components/schemas/CatBreed'
-    ...
-
 CatBreed:
   type: string
   enum: