From eee88ce38d4456bc3391fd27ed902cce4b21fa38 Mon Sep 17 00:00:00 2001 From: dberenbaum Date: Mon, 16 Oct 2023 16:31:17 -0400 Subject: [PATCH] fix broken links --- content/docs/api-reference/get_url.md | 2 +- content/docs/studio/rest-api.md | 4 +--- content/docs/user-guide/upgrade.md | 2 +- 3 files changed, 3 insertions(+), 5 deletions(-) diff --git a/content/docs/api-reference/get_url.md b/content/docs/api-reference/get_url.md index b62fce4016..e3f2646523 100644 --- a/content/docs/api-reference/get_url.md +++ b/content/docs/api-reference/get_url.md @@ -60,7 +60,7 @@ appropriate library, such as [`boto3`] or [`paramiko`]. [`boto3`]: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3.html#S3.Object.download_fileobj [`paramiko`]: - https://docs.paramiko.org/en/stable/api/sftp.html#paramiko.sftp_client.SFTPClient.get + https://docs.paramiko.org/en/latest/api/sftp.html#paramiko.sftp_client.SFTPClient.get diff --git a/content/docs/studio/rest-api.md b/content/docs/studio/rest-api.md index f9f2af4ed0..1490483df3 100644 --- a/content/docs/studio/rest-api.md +++ b/content/docs/studio/rest-api.md @@ -38,9 +38,7 @@ the latest version is returned. When your model is annotated in non-root [`dvc.yaml`] file (typical for monorepo case), model name will be constructed from two parts separated by colon: -`path/to/dvc/yaml:model_name`. For example, take a look at this -[model from example-get-started-experiments repo](https://studio.iterative.ai/user/aguschin/models/VtQdva13kMSPsN_N8004aQ==/pool-segmentation/v1.0.1). -Its full name that you need to use in API is `results/train:pool-segmentation`. +`path/to/dvc/yaml:model_name`. | header | desc | example value | | ------------- | --------------- | ------------- | diff --git a/content/docs/user-guide/upgrade.md b/content/docs/user-guide/upgrade.md index f62677adbe..a347f8a51b 100644 --- a/content/docs/user-guide/upgrade.md +++ b/content/docs/user-guide/upgrade.md @@ -84,7 +84,7 @@ Note that when using `--dvc-files` option, DVC will only migrate DVC files in -For [DVC remotes](/doc/user-guide/data-magement/remote-storage), there is no +For [DVC remotes](/doc/user-guide/data-management/remote-storage), there is no equivalent migration command since it is not possible to link between old and new locations on many remote filesystems. Instead, once you have migrated data locally and pushed to the remote, you may use `dvc gc -c` commands to remove