chore(recipe): updates md file

Author: Muhammad Rehan Alam

public/recipes/oauth/completion.md

@@ -5,35 +5,43 @@ You've successfully implemented a complete OAuth 2.0 Authorization Code Flow usi
 ## What You've Accomplished
 
 ### ✅ Step 1: Authorization Request Processed
+
 You validated an authorization request, generated a ticket, and prepared the authorization session.
 
 ### ✅ Step 2: Authorization Code Issued
+
 You simulated user consent and issued an authorization code to the client application.
 
 ### ✅ Step 3: Access Token Created
+
 You exchanged the authorization code for access and refresh tokens using the token endpoint.
 
 ### ✅ Step 4: Token Validated
+
 You introspected the access token to verify its validity, permissions, and metadata.
 
 ## Key Concepts Learned
 
 ### OAuth 2.0 Authorization Code Flow
+
 - The most secure OAuth flow for web and mobile applications
 - Separates authorization from token issuance
 - Uses short-lived authorization codes as intermediate credentials
 
 ### PKCE (Proof Key for Code Exchange)
+
 - Adds an extra layer of security with code challenges
 - Prevents authorization code interception attacks
 - Required for public clients and recommended for all
 
 ### Token Types
+
 - **Access Tokens**: Used to access protected resources
 - **Refresh Tokens**: Used to obtain new access tokens
 - **Bearer Tokens**: Anyone with the token can use it
 
 ### Security Best Practices
+
 - Tokens should be kept secure and never exposed
 - Authorization codes are single-use only
 - PKCE should always be used for enhanced security
@@ -44,37 +52,44 @@ You introspected the access token to verify its validity, permissions, and metad
 Now that you understand the OAuth flow, here's what you can do next:
 
 ### 🔧 Explore Service Settings
+
 - Configure token lifetimes and expiration policies
 - Set up custom scopes for fine-grained permissions
 - Enable additional OAuth features like OIDC
 
 ### 📚 Learn More OAuth Flows
+
 - **Client Credentials Flow**: For machine-to-machine authentication
 - **Refresh Token Flow**: For obtaining new access tokens
 - **Device Authorization Flow**: For devices with limited input
 
 ### 🎨 Customize Your Implementation
+
 - Add custom claims to tokens
 - Implement dynamic client registration
 - Set up token revocation endpoints
 
 ### 🛡️ Enhanced Security
+
 - Configure mTLS for certificate-bound tokens
 - Enable JWT access tokens
 - Set up token binding
 
 ## Resources
 
 ### Documentation
+
 - [Authlete Documentation](https://docs.authlete.com)
 - [OAuth 2.0 RFC 6749](https://tools.ietf.org/html/rfc6749)
 - [PKCE RFC 7636](https://tools.ietf.org/html/rfc7636)
 
 ### TypeScript SDK
+
 - [Authlete TypeScript SDK](https://github.com/authlete/authlete-typescript-sdk)
 - [SDK Documentation](https://authlete.github.io/authlete-typescript-sdk/)
 
 ### Support
+
 - [Authlete Support Portal](https://support.authlete.com)
 - [Community Forum](https://community.authlete.com)
 
@@ -83,7 +98,3 @@ Now that you understand the OAuth flow, here's what you can do next:
 You've taken an important step in understanding modern authentication and authorization. The skills you've learned here will help you build secure, standards-compliant applications.
 
 Ready to explore more? Head back to the dashboard to discover additional features and recipes!
-
----
-
-**Happy Coding! 🚀**

public/recipes/oauth/getting-started.md

@@ -26,15 +26,19 @@ Before you begin, ensure you have:
 This recipe consists of **4 interactive steps**:
 
 ### Step 1: Process Authorization Request
+
 Validate and process an authorization request from a client application. The SDK will check parameters, generate a ticket, and return client/scope information.
 
 ### Step 2: Issue Authorization Response
+
 Simulate user consent and issue an authorization code. This represents the user granting permission to the client application.
 
 ### Step 3: Exchange Code for Access Token
+
 Trade the authorization code for access and refresh tokens. This is the core token exchange in OAuth 2.0.
 
 ### Step 4: Introspect Access Token
+
 Validate the access token and retrieve its metadata. Resource servers use this to verify tokens before granting access.
 
 ## How It Works
@@ -55,6 +59,6 @@ Each step builds on the previous one:
 
 ## Ready to Start?
 
-Click "Next" to begin with the first step: **Process Authorization Request**
+Click "Start" to begin with the first step: **Process Authorization Request**
 
 The journey to understanding OAuth 2.0 starts here! 🚀