diff --git a/docs/guides/int_framework/intro.md b/docs/guides/int_framework/intro.md
index a2aebdf75..37c579159 100644
--- a/docs/guides/int_framework/intro.md
+++ b/docs/guides/int_framework/intro.md
@@ -294,7 +294,7 @@ By nesting commands inside a module that is tagged with [GroupAttribute] you can
 > [!NOTE]
 > To not use the command group's name as a prefix for component or modal interaction's custom id set `ignoreGroupNames` parameter to `true` in classes with [GroupAttribute]
 >
-> However, you have to be careful to prevent overlapping ids of buttons and modals
+> However, you have to be careful to prevent overlapping ids of buttons and modals.
 
 [!code-csharp[Command Group Example](samples/intro/groupmodule.cs)]
 
@@ -347,12 +347,12 @@ Methods like `AddModulesToGuildAsync()`, `AddCommandsToGuildAsync()`, `AddModule
 can be used to register cherry picked modules or commands to global/guild scopes.
 
 > [!NOTE]
-> [DontAutoRegisterAttribute] can be used on module classes to to prevent `RegisterCommandsGloballyAsync()` and `RegisterCommandsToGuildAsync()` from registering them to the Discord
+> [DontAutoRegisterAttribute] can be used on module classes to prevent `RegisterCommandsGloballyAsync()` and `RegisterCommandsToGuildAsync()` from registering them to the Discord.
 
 > [!NOTE]
 > In debug environment, since Global commands can take up to 1 hour to register/update,
 > it is adviced to register your commands to a test guild for your changes to take effect immediately.
-> You can use preprocessor directives to create a simple logic for registering commands as seen above
+> You can use preprocessor directives to create a simple logic for registering commands as seen above.
 
 ## Interaction Utility