🐛 Error in FlamaName component

Author: migduroli

content/docs/3-Fundamentals/2-Middlewares.mdx

@@ -104,7 +104,8 @@ app = Flama(
 )
 ```
 
-\<FlamaName /\> will wrap these middleware components around your application in the order they are provided. The first middleware in the list will be the outermost, processing the request first and the response last.
+<FlamaName /> will wrap these middleware components around your application in the order they are provided. The first
+middleware in the list will be the outermost, processing the request first and the response last.
 
 ## Example
 

content/docs/3-Fundamentals/3-Modules.mdx

@@ -285,4 +285,4 @@ This **I18nModule** example effectively shows:
 - How a module can initialise and provide an application-wide service (the **I18nService**)
 - Routes can then easily access this service through the registered module instance on the **app** object (e.g., `app.i18n`) to perform tasks like translating text based on language preferences.
 - The example also includes fallback mechanisms for missing translations and demonstrates how the module itself can offer convenient wrapper methods (like **I18nModule.translate()**)
-- The commented-out lines in the **on_startup()** method further hint at how such a module could register **Components** to make its services available through <FlamaName \>'s dependency injection, further enhancing decoupling and testability, which is a key aspect of <FlamaName />'s power and extensibility
+- The commented-out lines in the **on_startup()** method further hint at how such a module could register **Components** to make its services available through <FlamaName />'s dependency injection, further enhancing decoupling and testability, which is a key aspect of <FlamaName />'s power and extensibility