Skip to content

fix: typos in docs for Volumes #1984

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 25, 2025
Merged

fix: typos in docs for Volumes #1984

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion volumes/snapshots.html.markerb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ For options, refer to the [`fly volumes snapshots` docs](/docs/flyctl/volumes-sn

## Restore a volume from a snapshot

To procedure to restore data from a deleted volume is very similar, see [Restore a deleted volume](/docs/volumes/volume-manage/#restore-a-deleted-volume).
The procedure to restore data from a deleted volume is very similar, see [Restore a deleted volume](/docs/volumes/volume-manage/#restore-a-deleted-volume).

Restore the data from a volume by creating a new volume from a snapshot:

Expand Down
4 changes: 2 additions & 2 deletions volumes/volume-manage.html.markerb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,7 +110,7 @@ For options, refer to the [`fly volumes fork` docs](/docs/flyctl/volumes-fork/)

## Add a volume to an unmanaged Machine

For Machines that aren't managed with Fly Launch (`fly.toml` and `fly deploy`), you can create a volume and attach it when you clone a Machine. You can also [clone a Machine with a volume](/#clone-a-machine-with-a-volume) to get a new Machine with an empty volume.
For Machines that aren't managed with Fly Launch (`fly.toml` and `fly deploy`), you can create a volume and attach it when you clone a Machine. You can also [clone a Machine with a volume](#clone-a-machine-with-a-volume) to get a new Machine with an empty volume.

1. Create the volume in the same region as your app. For example:

Expand Down Expand Up @@ -239,4 +239,4 @@ For options, refer to the [`fly volumes snapshots` docs](/docs/flyctl/volumes-sn
- [Fly Volumes overview](/docs/volumes/overview/)
- [Manage volume snapshots](/docs/volumes/snapshots/)
- [Add volume storage to a Fly Launch app](/docs/apps/volume-storage/)
- [Scale an app with volumes](/docs/apps/scale-count/#scale-an-app-with-volumes)
- [Scale an app with volumes](/docs/apps/scale-count/#scale-an-app-with-volumes)