Skip to content

Commit 3dad026

Browse files
Update content/blog/entries/2020-04-03-nvmee-on-debian-on-aws/contents.lr
spelling correction Co-Authored-By: Brent Moran <brent@creativecommons.org>
1 parent 3654ec7 commit 3dad026

File tree

1 file changed

+1
-1
lines changed
  • content/blog/entries/2020-04-03-nvmee-on-debian-on-aws

1 file changed

+1
-1
lines changed

content/blog/entries/2020-04-03-nvmee-on-debian-on-aws/contents.lr

+1-1
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ At Creative Commons, we use the device specified during provisioning (ex.
3232
`/dev/xvdf`) to identify the correct NVMEe device. We then format it with a
3333
label that can be used mounting during subsequent reboots.
3434

35-
Thankfully, AWS docuemnts the the device specified during provisioning (ex. `/dev/xvdf`):
35+
Thankfully, AWS documents the the device specified during provisioning (ex. `/dev/xvdf`):
3636
> *For Nitro-based instances, the block device mappings that are specified in
3737
> the Amazon EC2 console when you are attaching an EBS volume or during
3838
> AttachVolume or RunInstances API calls are captured in the vendor-specific

0 commit comments

Comments
 (0)