Index: src/components/mod.rs
===================================================================
--- src/components/mod.rs	(revision ea9c50fd4a2217c17aee70ee1087b26aec0dea61)
+++ src/components/mod.rs	(revision 20de1d76cb3bfa57dd91c21754e5945f0209df53)
@@ -1,5 +1,4 @@
 //! The components module contains all shared components for our app. Components are the building blocks of dioxus apps.
-//! They can be used to defined common UI elements like buttons, forms, and modals. In this template, we define a Hero
-//! component and an Echo component for fullstack apps to be used in our app.
+//! They can be used to defined common UI elements like buttons, forms, and modals.
 
 mod transaction_accounts_component;
Index: src/main.rs
===================================================================
--- src/main.rs	(revision ea9c50fd4a2217c17aee70ee1087b26aec0dea61)
+++ src/main.rs	(revision 20de1d76cb3bfa57dd91c21754e5945f0209df53)
@@ -9,17 +9,13 @@
 mod views;
 
-/// The Route enum is used to define the structure of internal routes in our app. All route enums need to derive
-/// the [`Routable`] trait, which provides the necessary methods for the router to work.
+/// The Route enum is used to define the structure of internal routes in our app. All route enums need to derive the [`Routable`] trait, which provides the necessary methods for the router to work.
 /// 
-/// Each variant represents a different URL pattern that can be matched by the router. If that pattern is matched,
-/// the components for that route will be rendered.
+/// Each variant represents a different URL pattern that can be matched by the router. If that the components for that route will be rendered.
 #[derive(Debug, Clone, Routable, PartialEq)]
 #[rustfmt::skip]
 enum Route {
-    // The layout attribute defines a wrapper for all routes under the layout. Layouts are great for wrapping
-    // many routes with a common UI like a navbar.
+    // The layout attribute defines a wrapper for all routes under the layout. Layouts are great for wrapping many routes with a common UI like a navbar.
     #[layout(Navbar)]
-        // The route attribute defines the URL pattern that a specific route matches. If that pattern matches the URL,
-        // the component for that route will be rendered. The component name that is rendered defaults to the variant name.
+        // The route attribute defines the URL pattern that a specific route matches. If that pattern matches the URL, the component for that route will be rendered. The component name that is rendered defaults to the variant name.
         #[route("/")]
         TransactionAccounts {},
@@ -33,11 +29,9 @@
 
 fn main() {
-    // The `launch` function is the main entry point for a dioxus app. It takes a component and renders it with the platform feature
-    // you have enabled
+    // The `launch` function is the main entry point for a dioxus app. It takes a component and renders it with the platform feature you have enabled
     dioxus::launch(App);
 }
 
-/// App is the main component of our app. Components are the building blocks of dioxus apps. Each component is a function
-/// that takes some props and returns an Element. In this case, App takes no props because it is the root of our app.
+/// App is the main component of our app. Components are the building blocks of dioxus apps. Each component is a function that takes some props and returns an Element. In this case, App takes no props because it is the root of our app.
 ///
 /// Components should be annotated with `#[component]` to support props, better error messages, and autocomplete
@@ -46,12 +40,10 @@
     // The `rsx!` macro lets us define HTML inside of rust. It expands to an Element with all of our HTML inside.
     rsx! {
-        // In addition to element and text (which we will see later), rsx can contain other components. In this case,
-        // we are using the `document::Link` component to add a link to our favicon and main CSS file into the head of our app.
+        // In addition to element and text (which we will see later), rsx can contain other components. In this case, we are using the `document::Link` component to add a link to our favicon and main CSS file into the head of our app.
         document::Link { rel: "icon", href: FAVICON }
         document::Link { rel: "stylesheet", href: MAIN_CSS }
 
 
-        // The router component renders the route enum we defined above. It will handle synchronization of the URL and render
-        // the layouts and components for the active route.
+        // The router component renders the route enum we defined above. It will handle synchronization of the URL and render the layouts and components for the active route.
         Router::<Route> {}
     }
Index: src/views/mod.rs
===================================================================
--- src/views/mod.rs	(revision ea9c50fd4a2217c17aee70ee1087b26aec0dea61)
+++ src/views/mod.rs	(revision 20de1d76cb3bfa57dd91c21754e5945f0209df53)
@@ -1,11 +1,9 @@
-//! The views module contains the components for all Layouts and Routes for our app. Each layout and route in our [`Route`]
-//! enum will render one of these components.
+//! The views module contains the components for all Layouts and Routes for our app. Each layout and route in our [`Route`] enum will render one of these components.
 //!
 //!
-//! The [`Home`] and [`Blog`] components will be rendered when the current route is [`Route::Home`] or [`Route::Blog`] respectively.
+//! The [`TransactionAccounts`]  component will be rendered when the current route is [`Route::TransactionAccounts`].
 //!
 //!
-//! The [`Navbar`] component will be rendered on all pages of our app since every page is under the layout. The layout defines
-//! a common wrapper around all child routes.
+//! The [`Navbar`] component will be rendered on all pages of our app since every page is under the layout. The layout defines a common wrapper around all child routes.
 
 mod transaction_accounts;
Index: src/views/navbar.rs
===================================================================
--- src/views/navbar.rs	(revision ea9c50fd4a2217c17aee70ee1087b26aec0dea61)
+++ src/views/navbar.rs	(revision 20de1d76cb3bfa57dd91c21754e5945f0209df53)
@@ -6,12 +6,9 @@
 /// The Navbar component that will be rendered on all pages of our app since every page is under the layout.
 ///
-///
-/// This layout component wraps the UI of [Route::Home] and [Route::Blog] in a common navbar. The contents of the Home and Blog
-/// routes will be rendered under the outlet inside this component
+/// This layout component wraps the UI in a common navbar. The contents of the routes will be rendered under the outlet inside this component
 #[component]
 pub fn Navbar() -> Element {
     rsx! {
-        // The `Outlet` component is used to render the next component inside the layout. In this case, it will render either
-        // the [`Home`] or [`Blog`] component depending on the current route.
+        // The `Outlet` component is used to render the next component inside the layout. In this case, it will render component depending on the current route.
         Outlet::<Route> {}
 
Index: src/views/transaction_accounts.rs
===================================================================
--- src/views/transaction_accounts.rs	(revision ea9c50fd4a2217c17aee70ee1087b26aec0dea61)
+++ src/views/transaction_accounts.rs	(revision 20de1d76cb3bfa57dd91c21754e5945f0209df53)
@@ -2,5 +2,4 @@
 use dioxus::prelude::*;
 
-/// The TransactionAccounts page component that will be rendered when the current route is `[Route::Home]`
 #[component]
 pub fn TransactionAccounts() -> Element {