diff --git a/_posts/2025-05-21-secure-mcp-client.adoc b/_posts/2025-05-21-secure-mcp-client.adoc
index c8296e1059..e964c2ee0c 100644
--- a/_posts/2025-05-21-secure-mcp-client.adoc
+++ b/_posts/2025-05-21-secure-mcp-client.adoc
@@ -35,7 +35,7 @@ For example, let's temporarily update the diagram by removing the `AI Gemini`, r
 
 image::typical_oauth2_authorization.png[Typical OAuth2 Authorization,align="center"]
 
-You will very likely find similarities between this diagram and what you do in your projects. It is the OAuth2 authorization code flow is action: the user logs in to the application and authorizes it to access another service offering a poem creation on the user's behalf.
+You will very likely find similarities between this diagram and what you do in your projects. It is the OAuth2 authorization code flow in action: the user logs in to the application and authorizes it to access another service offering a poem creation on the user's behalf.
 
 The demo shows that Quarkus MCP Client can work effectively in such architectures by being able to use access tokens acquired during the user login, without you having to write any custom code.
 
@@ -102,7 +102,7 @@ import jakarta.inject.Inject;
 public class UserNameProvider {
 
     @Inject
-    SecurityIdentity securityIdentity; <1>
+    SecurityIdentity securityIdentity;
     
     @Tool(name = "user-name-provider", description = "Provides a name of the currently logged-in user") <1>
     @PermissionsAllowed("read:name") <2>