[FIX] *: run prettier

doc/architecture/rendering.md

@@ -13,7 +13,6 @@ A rendering occurs in two phases:
 - virtual rendering: this generates the virtual dom in memory, asynchronously
 - patch: applies a virtual tree to the screen (synchronously)
 
-
 There are several classes involved in a rendering:
 
 - components
@@ -21,9 +20,9 @@ There are several classes involved in a rendering:
 - fibers: small objects containing some metadata, associated with a rendering of
   a specific component
 
-
 Components are organized in a dynamic component tree, visible in the user
-interface.  Whenever a rendering is initiated in a component `C`:
+interface. Whenever a rendering is initiated in a component `C`:
+
 - a fiber is created on `C` with the rendering props information
 - the virtual rendering phase starts on C (will asynchronously render all the
   child components)
@@ -31,4 +30,3 @@ interface.  Whenever a rendering is initiated in a component `C`:
   animation frame, if the fiber is done
 - once it is done, the scheduler will call the task callback, which will apply
   the patch (if it was not cancelled in the meantime).
-

doc/reference/store.md

@@ -263,7 +263,7 @@ will perform a strict equality check and will update the component every time th
 check fails.
 
 Also, it may not be obvious, but it is crucial to remember that the selector
-function should return an object or an array.  The reason is that it needs to be
+function should return an object or an array. The reason is that it needs to be
 observed, otherwise the component would not be able to react to changes.
 
 ### `useDispatch`