docs: see preview env

Author: omermorad

content/recipes/automock.md

@@ -7,13 +7,11 @@ test development by automatically mocking class external dependencies.
 #### Introduction
 
 The dependency injection container is an essential component of the Nest module system.
-This container is utilized both during the testing phase and the application runtime.
-
+This container is utilized both during the testing phase and the application runtime. \
 Unit tests vary from other types of tests, such as integration tests, in that they must
 fully override providers/services within the DI container. External dependencies (providers)
 of the so-called "unit" should be totally isolated. That is, all dependencies within
-the DI container should be replaced by mock objects.
-
+the DI container should be replaced by mock objects. \
 As a result, loading the modules and replacing the providers inside them is a process that
 loops back on itself. Automock tackles this issue by automatically mocking all the
 external dependencies/providers, resulting in total isolation of the unit/class
@@ -31,9 +29,7 @@ Automock does not require any additional setup.
 Sinon will shortly be released.
 
 #### Example
-
 Consider the following cats service, which takes three constructor parameters:
-
 ```ts
 @@filename(cats.service)
 import { Injectable } from '@nestjs/core';
@@ -96,7 +92,6 @@ describe('Cats Service Unit Spec', () => {
 > info **info** The jest.Mocked<Source> utility type returns the Source type
 > wrapped with type definitions of Jest mock function. ([reference](https://jestjs.io/docs/mock-function-api/#jestmockedsource))
 
-\
 #### About `unit` and `unitRef`
 Let's examine the following code:
 
@@ -106,14 +101,12 @@ const { unit, unitRef } = Spec.create(CatsService).compile();
 
 Calling `.compile()` returns an object with two properties, `unit`, and `unitRef`.
 
-`unitRef` is a small container which holds the class external dependencies (that
+**`unitRef`** is a small container which holds the class external dependencies (that
 has been replaced with mocks).
 It has one method, `get()`, which returns the mocked dependency, thus,
 it enables all the stubbing options from Jest.
 
-> info **info** unitRef.get() takes a string (token) or a class (dependency)
-
-`unit` is the actual unit under test, it's an instance of the tested class.
+**`unit`** is the actual unit under test, it's an instance of the tested class.
 
 #### Handling Different Scenarios
 Nest offers different ways to retrieve dependencies from the DI container: