diff --git a/content/docs/command-reference/metrics/index.md b/content/docs/command-reference/metrics/index.md
index f6291dd6e6..5f134dd4ba 100644
--- a/content/docs/command-reference/metrics/index.md
+++ b/content/docs/command-reference/metrics/index.md
@@ -49,8 +49,7 @@ metrics.json  AUC       0.763981  0.801807   0.037826
 
 `dvc metrics` subcommands can be used on any
 [valid metrics files](#supported-file-formats). By default they use the ones
-specified in `dvc.yaml` (if any), for example `summary.json`
-below:
+specified in `dvc.yaml` (if any), for example `summary.json` below:
 
 ```yaml
 stages:
diff --git a/content/docs/command-reference/metrics/show.md b/content/docs/command-reference/metrics/show.md
index c341023dfc..27828c2020 100644
--- a/content/docs/command-reference/metrics/show.md
+++ b/content/docs/command-reference/metrics/show.md
@@ -27,7 +27,8 @@ target can even be directories, so that DVC recursively shows all metrics files
 inside.
 
 > Note that targets don't necessarily have to be defined in `dvc.yaml`. For that
-> reason, this command doesn't require an existing DVC project or Git repo to run in.
+> reason, this command doesn't require an existing DVC project or Git repo to
+> run in.
 
 An alternative way to display metrics is the `dvc metrics diff` command, which
 compares them with a previous version.