Skip to content

fix: NVM should be NVMe #9366

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
jaalah-akamai merged 2 commits into from
Jul 6, 2023
Merged

fix: NVM should be NVMe #9366

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1c90fa1
fix: NVM should be NVMe
jaalah Jul 5, 2023
12aa09c
Added changeset: Volume empty state misspelling of NVMe
jaalah Jul 5, 2023
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
5 changes: 5 additions & 0 deletions packages/manager/.changeset/pr-9366-fixed-1688578241873.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"@linode/manager": Fixed
---

Volume empty state misspelling of NVMe ([#9366](https://github.com/linode/manager/pull/9366))
2 changes: 1 addition & 1 deletion packages/manager/src/features/Volumes/VolumesLandingEmptyStateData.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ import type {
export const headers: ResourcesHeaders = {
description:
'Attach scalable, fault-tolerant, and performant block storage volumes to your Linode Compute Instances or Kubernetes Clusters.',
subtitle: 'NVM block storage service',
subtitle: 'NVMe block storage service',
title: 'Volumes',
};

Expand Down