Update oauth2-develop.md (#1037)

## Changes
- Changed wording from "decomposed" to "decoded" when talking about
parsing url parameters into objects
- Added missing bracket in the code example for generating a code
challenge
- Removed extra space

<!-- Please link to any applicable information (forum posts, bug
reports, etc.). -->

## Checks

By submitting your pull request for review, you agree to the following:

- [x] This contribution was created in whole or in part by me, and I
have the right to submit it under the terms of this repository's open
source licenses.
- [x] I understand and agree that this contribution and a record of it
are public, maintained indefinitely, and may be redistributed under the
terms of this repository's open source licenses.
- [x] To the best of my knowledge, all proposed changes are accurate.

Author: aiden-dev

content/en-us/cloud/open-cloud/oauth2-develop.md

@@ -46,7 +46,7 @@ the programming language of your choice to create the code verifier, calculate
 the hash, and perform Base64 encoding to generate the code challenge.
 
 When creating the code verifier, only use unreserved characters, including
-uppercase and lowercase letters (A-Z , a-z), decimal digits (0-9), hyphen (-),
+uppercase and lowercase letters (A-Z, a-z), decimal digits (0-9), hyphen (-),
 period (.), underscore (\_), and tilde (~), with a minimum length of 43
 characters and a maximum length of 128 characters.
 
@@ -67,6 +67,7 @@ function base64URLEncode(str) {
 // create sha256 hash from code verifier
 function sha256(buffer) {
   return crypto.createHash('sha256').update(buffer).digest(`base64`);
+}
 
 // create a random code verifier
 var code_verifier = base64URLEncode(crypto.randomBytes(32));
@@ -130,7 +131,7 @@ value previously) parameters.
 
 - The `code` parameter contains an authorization code that the app can
   exchange for an access token from the authorization server. Most backend
-  server languages have standard ways to access query parameters as decomposed
+  server languages have standard ways to access query parameters as decoded
   objects. You'll need to obtain the `code` parameter and use it to exchange
   for access tokens.