diff --git a/content/docs/user-guide/experiment-management/running-experiments.md b/content/docs/user-guide/experiment-management/running-experiments.md
index be5c73520c..4d95b6b349 100644
--- a/content/docs/user-guide/experiment-management/running-experiments.md
+++ b/content/docs/user-guide/experiment-management/running-experiments.md
@@ -61,10 +61,10 @@ and reproduces them.
 
 > 📖 See `dvc params` for more details.
 
-You could manually edit a params file and run an experiment using those as inputs. Since
-this is a common sequence, the built-in option `dvc exp run --set-param` (`-S`)
-is provided as a shortcut. It takes an existing param name and value, and
-updates the file on-the-fly before execution.
+You could manually edit a params file and run an experiment using those as
+inputs. Since this is a common sequence, the built-in option
+`dvc exp run --set-param` (`-S`) is provided as a shortcut. It takes an existing
+param name and value, and updates the file on-the-fly before execution.
 
 ```dvc
 $ cat params.yaml
@@ -193,9 +193,9 @@ outputs don't remain in the workspace.
 
 Subsequent uses of `dvc exp run` will resume from the latest checkpoint (using
 the latest cached versions of all outputs). To resume from a previous checkpoint
-(list them with `dvc exp show`), you must first `dvc exp apply` it before running
-it with `dvc exp run`. For `--queue` or `--temp` runs, use `--rev` to specify the
-checkpoint to resume from.
+(list them with `dvc exp show`), you must first `dvc exp apply` it before
+running it with `dvc exp run`. For `--queue` or `--temp` runs, use `--rev` to
+specify the checkpoint to resume from.
 
 Alternatively, use `--reset` to start over (discards previous checkpoints and
 their outputs). This is useful for re-training ML models, for example.