fix: contribution guide markdown errors fixed

Author: jankapunkt

CONTRIBUTING.md

@@ -7,18 +7,17 @@ in order to get your pull requests accepted.
 ## Disclose security vulnerabilities
 
 First things first:
-This project has strong security implications and we appreciate every help to
+This project has strong security implications, and we appreciate every help to
 improve security.
 
-**However, please read our [security policy](./SECURITY.md), before taking 
-actions.**
+**However, please read our [security policy](./SECURITY.md), before taking actions.**
 
 
 
 ## Guiding principles
 
 Before contributing to this project it is important to understand how this 
-project and it's collaborators views itself regarding it's scope and purpose.
+project and it's collaborators views itself regarding its scope and purpose.
 
 ### OAuth2 standard compliance
 
@@ -38,7 +37,7 @@ Extended readings:
 - [RFC 7636 - Proof Key for Code Exchange by OAuth Public Clients](https://datatracker.ietf.org/doc/html/rfc7636)
 - [RFC 7591 - OAuth 2.0 Dynamic Client Registration Protocol](https://datatracker.ietf.org/doc/html/rfc7591)
 
-### Framework agnostic
+### Framework-agnostic
 
 Design decisions and implementations are always done with keeping in mind, that
 there are multiple frameworks out there that use this project.
@@ -47,8 +46,7 @@ there are multiple frameworks out there that use this project.
 
 ## Development
 
-If you want to fix bugs or add new features, **please read this chapter and it's 
-sections carefully!**
+If you want to fix bugs or add new features, **please read this chapter and it's sections carefully!**
 
 ### No PR without issue
 
@@ -60,24 +58,24 @@ and discuss, whether this is a useful addition to the project.
 First, clone and install this project from source via
 
 ```bash
-$ git clone [email protected]:node-oauth/node-oauth2-server.git
-$ cd node-oauth2-server
-$ git checkout development # important! do not work on master!
-$ npm install
+git clone [email protected]:node-oauth/node-oauth2-server.git
+cd node-oauth2-server
+git checkout development # important! do not work on master!
+npm install
 ```
 
 From here you can run several scripts for development purposes:
 
 ```bash
-$ npm run test           # runs the tests once
-$ npm run test:coverage  # runs the tests including coverage
-$ npm run docs           # generates the API docs
+npm run test           # runs the tests once
+npm run test:coverage  # runs the tests including coverage
+npm run docs           # generates the API docs
 ```
 
 To work on a new feature or a fix please create a new branch:
 
 ```bash
-$ git checkout -b feature-xyz # or fix-xyz
+git checkout -b feature-xyz # or fix-xyz
 ```
 
 ### Coding rules
@@ -93,8 +91,9 @@ with ticket number at the end of summary:
 ```
 <type>(<scope>): <short summary> #<issue number>
 ```
+
 Summary in present tense. Not capitalized. No period at the end.
-The <type> and <summary> fields are mandatory, the (<scope>) and #<number> field is optional.
+The `<type>` and `<summary>` fields are mandatory, the `(<scope>)` and `#<number>` fields are optional.
 
 ### Run the tests before committing
 
@@ -105,13 +104,13 @@ the history with commits, that are solely targeting lint fixes.
 You can run the tests via
 
 ```bash
-$ npm run test
+npm run test
 ```
 
 or  
 
 ```bash
-$ npm run test:coverage
+npm run test:coverage
 ```
 
 to see your coverage.
@@ -152,7 +151,7 @@ Also make sure, to comply with the following list:
 
 #### Review process
 
-Finally your PR needs to pass the review process:
+Finally, your PR needs to pass the review process:
 
 - A certain amount of maintainers needs to review and accept your PR
 - Please **expect change requests**! They will occur and are intended to improve
@@ -173,7 +172,7 @@ If you want to contribute to the docs, please get familiar with Vitepress: https
 
 ### Setting up docs
 
-You need NPM to setup the docs using the following:
+You need NPM to set up the docs using the following:
 
 ```shell
 npm install
@@ -192,3 +191,4 @@ to generate the api docs.
 
 ### Building the docs
 
+Run `npm run docs:build` to build the docs.

docs/api/utils/crypto-util.md

@@ -0,0 +1,19 @@
+<a name="module_CryptoUtil"></a>
+
+## CryptoUtil
+<a name="module_CryptoUtil..createHash"></a>
+
+### CryptoUtil~createHash(algorithm, data, [encoding], output) ⇒ <code>Buffer</code> \| <code>string</code>
+Creates a new hash by given algorithm, data and digest encoding.
+Defaults to sha256.
+
+**Kind**: inner method of [<code>CryptoUtil</code>](#module_CryptoUtil)  
+**Returns**: <code>Buffer</code> \| <code>string</code> - if {output} is undefined, a {Buffer} is returned, otherwise a {String}  
+
+| Param | Type | Description |
+| --- | --- | --- |
+| algorithm | <code>string</code> | the hash algorithm, default is 'sha256' |
+| data | <code>Buffer</code> \| <code>string</code> \| <code>TypedArray</code> \| <code>DataView</code> | the data to hash |
+| [encoding] | <code>string</code> | optional, the encoding of the input |
+| output | <code>&#x27;base64&#x27;</code> \| <code>&#x27;base64url&#x27;</code> \| <code>&#x27;binary&#x27;</code> \| <code>&#x27;hex&#x27;</code> \| <code>undefined</code> | optional, the desired output type |
+

docs/guide/grant-types.md

@@ -14,8 +14,6 @@ scenario of use cases.
 An authorization code is a credential representing the resource owner's authorization
 (to access its protected resources) which is used by the client to obtain an access token.
 
-TODO: overview of the workflow with functions involved
-
 ## Refresh Token Grant Type
 
 **Defined in:** [Section 6 of RFC 6749](https://www.rfc-editor.org/rfc/rfc6749#section-6).
@@ -25,8 +23,6 @@ TODO: overview of the workflow with functions involved
 If the authorization server issued a refresh token to the client,
 the client can request a refresh of their authorization token.
 
-TODO: overview of the workflow with functions involved
-
 ## Password Grant Type
 
 ::: warning