Merge pull request #2288 from sberyozkin/secure_mcp_server_blog_fixes

Typo fixes in the Secure MCP server post

Author: sberyozkin

_posts/2025-04-28-secure-mcp-sse-server.adoc

@@ -200,7 +200,7 @@ Note the use of the `%prod.` prefixes. It ensures the configuration properties p
 
 Currently, MCP clients can not use the authorization code flow themselves. Therefore, we implement an OAuth2 login endpoint that will return a GitHub token for the user to use with MCP clients, which can work with bearer tokens.
 
-Add another dependency: to support Qute templates:
+Add another dependency to support Qute templates:
 
 [source,xml]
 ----
@@ -249,7 +249,7 @@ public class LoginResource {
     }
 }
 ----
-<1> GitHub access tokens are binary and Quarkus OIDC indirectly verifies them by using them to request GutHub specific `UserInfo` representation.
+<1> GitHub access tokens are binary and Quarkus OIDC indirectly verifies them by using them to request GitHub specific `UserInfo` representation.
 <2> `AccessTokenCredential` is used to capture a binary GitHub access token.
 <3> After the user logs in to GitHub and is redirected to this endpoint, the access token will be returned to the user in an HTML page generated with a simple https://github.com/quarkiverse/quarkus-mcp-server/tree/main/samples/secure-mcp-sse-server/src/main/resources/templates/accessTokenPage.html[Qute template].
 Of course, you would not do that in a real application. It is just an example to demonstrate the capability.