style: fix prettier issues

docs/api/subgraphs/protocol/02-structure.mdx

@@ -125,9 +125,10 @@ you don't need to worry about `proxenders` and `proxy` if you're not looking to
 
 :::
 
-[In V2.0] While not mandatory for the core functionality, Sablier made use of [PRBProxy](https://github.com/paulrberg/prb-proxy)
-in its [periphery](https://github.com/sablier-labs/v2-periphery. The official client interfaces provided support for functionality
-exposed through both EOAs and this proxy integration, at the same time.
+[In V2.0] While not mandatory for the core functionality, Sablier made use of
+[PRBProxy](https://github.com/paulrberg/prb-proxy) in its [periphery](https://github.com/sablier-labs/v2-periphery. The
+official client interfaces provided support for functionality exposed through both EOAs and this proxy integration, at
+the same time.
 
 For streams created within this "extended" ecosystem, a few attributes and entities will change meaning as such:
 

docs/concepts/protocol/07-statuses.md

@@ -22,7 +22,7 @@ A stream status can have one out of two "temperatures":
 
 | Temperature | Statuses                    | Description                                                                                    |
 | :---------- | :-------------------------- | :--------------------------------------------------------------------------------------------- |
-| Warm        | Pending, Streaming          | The passage of time alone <ins>can</ins> change the status.                                |
+| Warm        | Pending, Streaming          | The passage of time alone <ins>can</ins> change the status.                                    |
 | Cold        | Settled, Canceled, Depleted | The passage of time alone <ins>cannot</ins> change the status. Only a user action can do this. |
 
 ## Diagram