[go: nahoru, domu]

Skip to content
This repository has been archived by the owner on Aug 4, 2023. It is now read-only.

Commit

Permalink
fix typos (#556)
Browse files Browse the repository at this point in the history
  • Loading branch information
suryajak authored and whitlockjc committed Jan 3, 2018
1 parent 0cea535 commit f3650ec
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/Swagger_Validation.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@ When validating Swagger document(s), the Swagger Specification document for the
single source of truth for validation. To help aid in Swagger document validation, the Swagger project provides
[JSON Schema][json-schema] file(s) but in the end, the Swagger Specification document is the real source of truth and
the document swagger-tools tries to adhere to. swagger-tools uses the provided JSON Schema file(s) to do the initial
structural validation of the Swagger document(s) but that is just the beginnging. There are some situations where the
JSON Schema does not fullfil the complete contract as described in the Swagger specification documentation. This is
structural validation of the Swagger document(s) but that is just the beginning. There are some situations where the
JSON Schema does not fulfill the complete contract as described in the Swagger specification documentation. This is
where swagger-tools has stepped in to help pave the way for doing full Swagger document validation. swagger-tools
starts all Swagger document validation using the JSON Schema file(s) and only once that validation passes will
swagger-tools go through each pertinent _semantic_ validation in its catalog to do the rest of the validation.
Expand Down

0 comments on commit f3650ec

Please sign in to comment.