Skip to content

Commit b37c6ab

Browse files
committed
gdrive: updates to User Guide page
1 parent 40afbb4 commit b37c6ab

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

public/static/docs/user-guide/setup-google-drive-remote.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,8 @@ API connections, and its
4242

4343
⚠️ It should be safe to share **client ID** and **client secret** among your
4444
team. These credentials are only used to generate the
45-
[authorization](#authorization) DVC will later need in order to connect to the
46-
Google Drive.
45+
[authorization](#authorization) URL DVC will later prompt to visit in order to
46+
connect to the Google Drive.
4747

4848
> Note that Google Drive API has usage limits/quotas per credentials in a
4949
> _project_ (which you can review in the
@@ -108,7 +108,6 @@ guide you through granting the necessary access permissions. On success, the
108108
token data will be cached in a Git-ignored directory located in
109109
`.dvc/tmp/gdrive-user-credentials.json`.
110110

111-
⚠️ In order to prevent unauthenticated access to your Google Drive, **do not
112-
share access token data with others**. Each team member should have
113-
[separate access](https://support.google.com/drive/answer/7166529) to the
114-
appropriate Google Drive resources, and generate their own tokens.
111+
⚠️ In order to prevent unauthorized access to your Google Drive, **do not share
112+
access token data with others**. Each team member should generate their own
113+
tokens.

0 commit comments

Comments
 (0)