@@ -4,7 +4,7 @@ All contributions to the Python JwtConnect packages are welcome!
44
55Note that as this library is planned to be used in high-profile production code,
66we insist on a very high standards for the code and design, but don't feel shy:
7- discuss your plans over
7+ discuss your plans over
88[ GitHub Issues] ( https://github.com/openid/JWTConnect-Python-OidcMsg/issues ) and the
99[ mailing list] ( http://lists.openid.net/mailman/listinfo/openid-specs-ab ) , and
1010send in those pull requests!
@@ -42,14 +42,14 @@ requests).
4242Before you work on a big new feature, get in touch to make sure that your work
4343is inline with the direction of the project and get input on your architecture.
4444You can file an [ Issue] ( https://github.com/openid/JWTConnect-Python-OidcMsg/issues )
45- discussing your proposal, or email the
46- [ list] ( http://lists.openid.net/mailman/listinfo/openid-specs-ab ) .
45+ discussing your proposal, or email the
46+ [ list] ( http://lists.openid.net/mailman/listinfo/openid-specs-ab ) .
4747
4848## Coding Standards
4949
5050The JWTCOnnect-Python-OidcMsg library follows the
51- [ PEP8] ( https://www.python.org/dev/peps/pep-0008/ )
52- coding style for Python implementations. Please review your own code
51+ [ PEP8] ( https://www.python.org/dev/peps/pep-0008/ )
52+ coding style for Python implementations. Please review your own code
5353for adherence to the standard.
5454
5555## Pull Request Reviews
0 commit comments