Apply suggestions from code review

Co-authored-by: Lukáš Tinkl <lukast@status.im>
Co-authored-by: Noelia  <97019400+noeliaSD@users.noreply.github.com>

docs/FURPS/tablet-build.md

@@ -1,4 +1,4 @@
-# Table Build FURPS ([#17941](https://github.com/status-im/status-desktop/issues/17941))
+# Tablet Build FURPS ([#17941](https://github.com/status-im/status-desktop/issues/17941))
 
 ## Functionality
 - Partial feature parity with desktop app expected - no keycard, biometrics and dapps. To be added later.

docs/FURPS/ui-modularization.md

@@ -11,14 +11,14 @@
 - Document architectural patterns and usage conventions to reduce ambiguity during development.
 
 ## Reliability
-- Reduce tight coupling between backend logic and UI to minimize bugs from implementation side effects.
+- Reduce tight coupling between business logic and UI to minimize bugs from implementation side effects.
 - Ensure predictable data flow with read-only modules and strictly typed store usage.
 - Safeguard against improper store usage with guidelines on instantiation and component scope.
 
 ## Performance
 - Avoid unnecessary data duplication and propagation through read-only modules and centralized ground truth state.
 - Minimize transformation overhead by using adaptors only when necessary for UI display logic.
-- Ensure UI responsiveness by decoupling backend processing from rendering logic.
+- Ensure UI responsiveness by decoupling business logic processing from rendering logic.
 
 ## Supportability
 - Use strictly typed interfaces (`no var`) to catch issues at compile time and improve tooling support.