diff --git a/sections/appendix/ui_tests.typ b/sections/appendix/ui_tests.typ
index 293823f..054b4b8 100644
--- a/sections/appendix/ui_tests.typ
+++ b/sections/appendix/ui_tests.typ
@@ -79,6 +79,10 @@ appreciated the design while providing valuable advice on how to improve it.
 - *Conclusion*
 Feedback around navigation and readability was positive, mostly attributed to
 the currently simple UI. It's important to note that readability is already
-configured by the user or by using system defaults. Regarding the layout and
-design, there will be improvements made by templating a few elements, which fixes the issue of inconsistent design. Features such as collapsing subcategories have to be
-discussed further, to determine if it's necessary and if fit in the timeframe.
+configured by the user or by using system defaults. ReSet doesn't overwrite 
+these configurations to keep a consistent look throughout the user's system. 
+Concerning the layout and design, there will be improvements made by templating 
+common UI building blocks, which will fix the issue of inconsistent design and 
+make it easier to keep it consistent. Features such as collapsing subcategories 
+have to be discussed further, to determine if it's necessary and if fit in the 
+timeframe.
diff --git a/sections/implementation/ui_design.typ b/sections/implementation/ui_design.typ
index ce4a299..3510b4b 100644
--- a/sections/implementation/ui_design.typ
+++ b/sections/implementation/ui_design.typ
@@ -133,8 +133,7 @@ full screen.
 On top of that, the settings are structured in a hierarchical order, which
 allows us to have a breadcrumb menu similar to file paths. This can help users
 backtrack to previous sections without having to restart their search from the
-beginning. With this hierarchical order, it is also possible to use the Back
-button on the mouse for navigation.
+beginning. This hierarchical order allows users to navigate using the Back button. 
 #align(
   center, [#figure(
       img("windowsBreadcrumb.png", width: 75%), caption: [Windows 11 breadcrumb menu],
diff --git a/sections/literature.typ b/sections/literature.typ
index aec73d6..938baf7 100644
--- a/sections/literature.typ
+++ b/sections/literature.typ
@@ -28,7 +28,7 @@ Krug's rules:
   This rule depends heavily on what the possible user base is, an IDE has
   different users to a general messaging application.
 
-  For the example, the application Blueman introduced in
+  For example, the application Blueman introduced in
   @Analysisofexistingapplications is used.
   #figure(
     align(center, [#image("../figures/bluetooth_manager.png", width: 80%)]), caption: [Screenshot of Bluetooth manager],
@@ -45,7 +45,7 @@ Krug's rules:
   devices as expected. The question now is how to connect to a specific device.
   Users who understand Bluetooth terminology will likely proceed with the key
   icon, which means pairing for this application. However, there is a chance that
-  users will first try the checkmark icon in order to connect to the device.
+  users will first try the checkmark icon to connect to the device.
 
   In this case, the icons could be improved to represent a more technology-neutral
   design.
diff --git a/sections/projects.typ b/sections/projects.typ
index 99a55cf..f6b795d 100644
--- a/sections/projects.typ
+++ b/sections/projects.typ
@@ -267,7 +267,7 @@ achieve. Blueman is written in Python and GTK3.
   cell(
     [The user interface for Blueman can be rather confusing, for example: there is no
       obvious connect button, which might lead to a user trying to re-pair a device
-      instead of connecting to it. (pairing is the \u{2713} button)\
+      instead of connecting to it. (pairing is the \u{2713} button).
       Blueman also tends to use older icon design.], cell_align: left, bold: false, font_size: 11pt,
   ),
   cell("X", bold: true, cell_align: center),