Update website/docs/docs/api/persist.md

Co-authored-by: Jørn A. Myrland <[email protected]>

website/docs/docs/api/persist.md

@@ -268,13 +268,13 @@ have persisted state based on a previous version of your store model. The user's
 persisted state may not align with that of your new store model, which could
 result in errors when a component tries to consume/update the store.
 
-By default the persist API utilizes the mergeDeep strategy (you can read more
-about merge strategies further below). The mergeDeep strategy attempts to
+By default the persist API utilizes the `mergeDeep` strategy (you can read more
+about merge strategies further below). The `mergeDeep` strategy attempts to
 perform an optimistic merge of the persisted state against the store model.
 Where it finds that the persisted state is missing keys that are present in the
 store model, it will ensure to use the respective state from the store model. It
 will also verify the types of data at each key. If there is a misalignment
-(ignoring null or undefined) then it will opt for using the data from the store
+(ignoring `null` or `undefined`) then it will opt for using the data from the store
 model instead as this generally indicates that the respective state has been
 refactored.