Restyled by prettier

content/docs/start/data-pipelines.md

@@ -144,17 +144,18 @@ stages:
 </details>
 
 There's no need to use `dvc add` for DVC to track stage outputs (`data/prepared`
-in this case); `dvc stage add` and `dvc exp run` takes care of this. You only need
-to run `dvc push` if you want to save them to
+in this case); `dvc stage add` and `dvc exp run` takes care of this. You only
+need to run `dvc push` if you want to save them to
 [remote storage](/doc/start/data-and-model-versioning#storing-and-sharing),
 (usually along with `git commit` to version `dvc.yaml` itself).
 
 ## Dependency graphs (DAGs)
 
-By using `dvc stage add` multiple times, and specifying <abbr>outputs</abbr> of a
-stage as <abbr>dependencies</abbr> of another one, we can describe a sequence of
-commands which gets to a desired result. This is what we call a _data pipeline_
-or [_dependency graph_](https://en.wikipedia.org/wiki/Directed_acyclic_graph).
+By using `dvc stage add` multiple times, and specifying <abbr>outputs</abbr> of
+a stage as <abbr>dependencies</abbr> of another one, we can describe a sequence
+of commands which gets to a desired result. This is what we call a _data
+pipeline_ or
+[_dependency graph_](https://en.wikipedia.org/wiki/Directed_acyclic_graph).
 
 Let's create a second stage chained to the outputs of `prepare`, to perform
 feature extraction:
@@ -171,7 +172,6 @@ The `dvc.yaml` file is updated automatically and should include two stages now.
 
 <details>
 
-
 ### 💡 Expand to see what happens under the hood.
 
 The changes to the `dvc.yaml` should look like this:
@@ -243,7 +243,7 @@ parameters for the training stage:
 1. Open `params.yaml` and change `n_est` to `100`, and
 2. (re)run `dvc exp run`.
 
->> Link to experiments trail here
+> > Link to experiments trail here
 
 You should see:
 
@@ -259,8 +259,8 @@ the intermediate results are being reused.
 
 Now, let's change it back to `50` and run `dvc exp run` again:
 
->> It looks these manual changes are a bit tedious. We can replace these with
->> code or data changes that can't be captured with `dvc exp run -S`
+> > It looks these manual changes are a bit tedious. We can replace these with
+> > code or data changes that can't be captured with `dvc exp run -S`
 
 ```dvc
 $ dvc exp run