chore: fix some comments (#3101)

Signed-off-by: careworry <worrycare@outlook.com>

design.md

@@ -145,7 +145,7 @@ The second part is generating a swagger spec from go code based on annotations a
 
 The goal of this code generation is to just take care of the boilerplate.
 It uses a very small runtime to accommodate the swagger workflow. These are just small helpers for sharing some common
-code.  The server application uses plain go http do do its thing. All other code is generated so you can read what it
+code.  The server application uses plain go http do its thing. All other code is generated so you can read what it
 does and if you think it's worth it.
 
 The go server api generator however won't reuse those templates but define its own set, because currently no proper go support exists in that project. Once I'm happy with what they generate I'll contribute them back to the swagger-codegen project.

docs/contributing/guidelines.md

@@ -17,4 +17,4 @@ We try to remain consistent across repositories regarding linting rules.
 
 # Vendoring
 
-All `go-openapi` and `go-swagger` repositories have adopted go modules and and are no longer using vendoring.
+All `go-openapi` and `go-swagger` repositories have adopted go modules and are no longer using vendoring.

docs/faq/faq_documenting.md

@@ -45,7 +45,7 @@ and severely bloated the size of my binary.
 I'm reluctant to do so at this point in time because a git submodule break go-gettability.
 
 >I've had it included at one point but it's so much of a moving target that it would always be outdated.
->On top of it it are a lot of javascript and html files and people haven't been over the moon when go-swagger gets
+>On top of it is a lot of javascript and html files and people haven't been over the moon when go-swagger gets
 >vendored and they see all of that.
 
 Originally from issue [#370](https://github.com/go-swagger/go-swagger/issues/370).

fixtures/goparsing/classification/transitive/mods/pet.go

@@ -17,7 +17,7 @@ package mods
 // Pet represents a pet in our store
 //
 // This model is not explicitly mentioned in the import paths,
-// but because it it transitively required by the order
+// but because it is transitively required by the order
 // it should also be collected.
 //
 // swagger:model pet

generator/operation.go

@@ -788,7 +788,7 @@ func (b *codeGenOpBuilder) MakeParameter(receiver string, resolver *typeResolver
 				return GenParameter{}, err
 			}
 			res.Child = &pi
-			// Propagates HasValidations from from child array
+			// Propagates HasValidations from child array
 			hasChildValidations = pi.HasValidations
 		}
 		res.IsNullable = !param.Required && !param.AllowEmptyValue