fix typo

CONTRIBUTING.md

@@ -78,7 +78,7 @@ For [Vendor Extensions](https://github.com/OAI/OpenAPI-Specification/blob/master
 To add test cases (optional) covering the change in the code generator, please refer to [tests](https://github.com/swagger-api/swagger-codegen/tree/3.0.0/modules/swagger-codegen/src/test/java/io/swagger/codegen/v3/service)
 
 To test the templates, please perform the following:
-- Update the [Petstore](http://petstore.swagger.io/) sample by running the shell script under `bin` folder. For example, run `./bin/ruby-petstore.sh` to update the Ruby PetStore API client under [`samples/client/petstore/python`](https://github.com/swagger-api/swagger-codegen/tree/3.0.0/samples/client/petstore/python) For Windows, the batch files can be found under `bin\windows` folder. (If you find that there are new files generated or unexpected changes as a result of the update, that's not unusual as the test cases are added to the OpenAPI/Swagger spec from time to time. If you've questions or concerns, please open a ticket to start a discussion)
+- Update the [Petstore](http://petstore.swagger.io/) sample by running the shell script under `bin` folder. For example, run `./bin/python-petstore.sh` to update the python PetStore API client under [`samples/client/petstore/python`](https://github.com/swagger-api/swagger-codegen/tree/3.0.0/samples/client/petstore/python) For Windows, the batch files can be found under `bin\windows` folder. (If you find that there are new files generated or unexpected changes as a result of the update, that's not unusual as the test cases are added to the OpenAPI/Swagger spec from time to time. If you've questions or concerns, please open a ticket to start a discussion)
 - Run the tests in the sample folder (some languages may not contain unit testing for Petstore and we're looking for contribution from the community to implement those tests)
 - Finally, git commit the updated samples files: `git commit -a`
   (`git add -A` if added files with new test cases)