From cd991b5f4b474e90c972f4e9d5f003e6e10ff309 Mon Sep 17 00:00:00 2001 From: "restyled-io[bot]" <32688539+restyled-io[bot]@users.noreply.github.com> Date: Mon, 13 Mar 2023 12:18:12 -0400 Subject: [PATCH] Restyled by prettier (#4388) Co-authored-by: Restyled.io --- .../docs/user-guide/data-management/remote-storage/ssh.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/docs/user-guide/data-management/remote-storage/ssh.md b/content/docs/user-guide/data-management/remote-storage/ssh.md index c393a48107..a1d3e5d01c 100644 --- a/content/docs/user-guide/data-management/remote-storage/ssh.md +++ b/content/docs/user-guide/data-management/remote-storage/ssh.md @@ -72,10 +72,10 @@ through Git. See `dvc config`. -Using a private key is usually the recommended way to authenticate an SSH connection, -and it should be saved in a key file. You can set its path as shown below. -Often these require a passphrase to use as well: You can set up DVC to ask for -it each time, or set it directly. +Using a private key is usually the recommended way to authenticate an SSH +connection, and it should be saved in a key file. You can set its path as shown +below. Often these require a passphrase to use as well: You can set up DVC to +ask for it each time, or set it directly. ```cli $ dvc remote modify --local myremote keyfile /path/to/keyfile