Skip to content

Commit c578f8b

Browse files
fix(doc): architecture: duplicated images and list style;
1 parent a789910 commit c578f8b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

ARCHITECTURE.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -113,13 +113,13 @@ You won't find any raw Strings. Bytes for hashing/encryption are `Vec<u8>` (not
113113

114114
This app has a simple and typical logging system: [`wasm-logger`](https://crates.io/crates/wasm-logger) + [`log`](https://crates.io/crates/log) crates. If you want to log something, then just use any suitable for you macros from the `log` crate. All logs will be written into the browser's console. This is how it looks:
115115

116-
![](/public/img/architecture/logs_exmaple.png) ![](/public/img/architecture/logs_exmaple.png)
116+
![](/public/img/architecture/logs_exmaple.png)
117117

118118
3. Inform user about everything.
119119

120120
You have two main ways how to tell the user that something went wrong:
121121

122-
# Spawn notifications using the [`use_notifications`](https://yn-docs.qkation.com/yew_notifications/fn.use_notification.html) hook from the [`yew_notifications`](https://github.com/TheBestTvarynka/yew-notifications) crate.
123-
# Different UI tricks like painting the input component in red, on-page messages, etc. Example:
122+
* Spawn notifications using the [`use_notifications`](https://yn-docs.qkation.com/yew_notifications/fn.use_notification.html) hook from the [`yew_notifications`](https://github.com/TheBestTvarynka/yew-notifications) crate.
123+
* Different UI tricks like painting the input component in red, on-page messages, etc. Example:
124124

125-
![](/public/img/architecture/invalid_input.png) ![](/public/img/architecture/invalid_input.png)
125+
![](/public/img/architecture/invalid_input.png)

0 commit comments

Comments
 (0)