From: Tokunori Ikegami Date: Sat, 9 Jul 2022 03:43:57 +0000 (+0900) Subject: docs: Correct spelling check error X-Git-Tag: v2.1-rc0~9^2 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=c1894f69fe7d0b04a17c539e241c1024a4922e31;p=users%2Fsagi%2Fnvme-cli.git docs: Correct spelling check error Signed-off-by: Tokunori Ikegami --- diff --git a/Documentation/cmd-plugins.txt b/Documentation/cmd-plugins.txt index 4e66cf14..2ab6c682 100644 --- a/Documentation/cmd-plugins.txt +++ b/Documentation/cmd-plugins.txt @@ -65,7 +65,7 @@ linknvme:nvme-transcend-badblock[1]:: Retrieve Transcend NVMe device's bad blocks linknvme:nvme-transcend-healthvalue[1]:: - Use NVMe SMART table to analyse the health value of Transcend device + Use NVMe SMART table to analyze the health value of Transcend device linknvme:nvme-virtium-show-identify[1]:: Show a complete detail of identify device information in json format diff --git a/Documentation/cmds-main.txt b/Documentation/cmds-main.txt index ab8ee3bb..58a8094f 100644 --- a/Documentation/cmds-main.txt +++ b/Documentation/cmds-main.txt @@ -44,7 +44,7 @@ linknvme:nvme-smart-log[1]:: Retrieve Smart Log linknvme:nvme-ana-log[1]:: - Retreive ANA(Asymmetric Namespace Access) Log + Retrieve ANA(Asymmetric Namespace Access) Log linknvme:nvme-endurance-log[1]:: Retrieve endurance Log @@ -236,7 +236,7 @@ linknvme:nvme-nvm-id-ns-lba-format[1]:: NVMe Identify Namespace NVM Command Set for the specified LBA Format index linknvme:nvme-persistent-event-log[1]:: - Retrieve Presistent Event Log + Retrieve Persistent Event Log linknvme:nvme-predictable-lat-log[1]:: Retrieve Predictable Latency per Nvmset Log diff --git a/Documentation/nvme-attach-ns.txt b/Documentation/nvme-attach-ns.txt index a5d34712..64ab9d1a 100644 --- a/Documentation/nvme-attach-ns.txt +++ b/Documentation/nvme-attach-ns.txt @@ -26,11 +26,11 @@ OPTIONS -c :: -controllers=:: The comma separated list of controller identifiers to attach - the namesapce too. + the namespace too. EXAMPLES -------- - Attach namspace to the controller: + Attach namespace to the controller: # nvme attach-ns /dev/nvme1 -n 0x2 -c 0x21 diff --git a/Documentation/nvme-compare.txt b/Documentation/nvme-compare.txt index f082a33e..11299bd7 100644 --- a/Documentation/nvme-compare.txt +++ b/Documentation/nvme-compare.txt @@ -55,10 +55,10 @@ OPTIONS -y :: --metadata-size=:: - Size of metadata to be trasnferred in bytes. + Size of metadata to be transferred in bytes. -r :: ---ref-tag=:: +--ref-tag=:: Reference Tag for Protection Information -d :: @@ -106,8 +106,8 @@ metadata is passes. --dir-type=:: Optional directive type. The nvme-cli only enforces the value be in the defined range for the directive type, though the NVMe - specifcation (1.3a) defines only one directive, 01h, for write - stream idenfiers. + specification (1.3a) defines only one directive, 01h, for write + stream identifiers. -S :: --dir-spec=:: @@ -146,7 +146,7 @@ metadata is passes. data protection processing. --force:: - Ignore namespace is currently busy and perfome the operation + Ignore namespace is currently busy and performed the operation even though. EXAMPLES diff --git a/Documentation/nvme-connect-all.txt b/Documentation/nvme-connect-all.txt index 605d2459..b449955d 100644 --- a/Documentation/nvme-connect-all.txt +++ b/Documentation/nvme-connect-all.txt @@ -43,7 +43,7 @@ connect-all commands to run. If no @SYSCONFDIR@/nvme/discovery.conf file exists, the command will quit with an error. Otherwise a specific Discovery Controller should be specified using the ---transport, --traddr and if necessary the --trsvcid and a Diѕcovery +--transport, --traddr and if necessary the --trsvcid and a Discovery request will be sent to the specified Discovery Controller. See the documentation for the nvme-discover(1) command for further diff --git a/Documentation/nvme-copy.txt b/Documentation/nvme-copy.txt index d6452ec0..1fad952d 100644 --- a/Documentation/nvme-copy.txt +++ b/Documentation/nvme-copy.txt @@ -88,8 +88,8 @@ OPTIONS -T :: Optional directive type. The nvme-cli only enforces the value be in the defined range for the directive type, though the NVMe - specifcation (1.3a) defines only one directive, 01h, for write - stream idenfiers. + specification (1.3a) defines only one directive, 01h, for write + stream identifiers. --dir-spec=:: -S :: diff --git a/Documentation/nvme-create-ns.txt b/Documentation/nvme-create-ns.txt index 7fd64f4e..a17c70db 100644 --- a/Documentation/nvme-create-ns.txt +++ b/Documentation/nvme-create-ns.txt @@ -53,7 +53,7 @@ OPTIONS -a:: --anagrp-id:: - ANA Gorup Identifier. If this value is 0h specifies + ANA Group Identifier. If this value is 0h specifies that the controller determines the value to use -i :: diff --git a/Documentation/nvme-device-self-test.txt b/Documentation/nvme-device-self-test.txt index b7273a02..62bba88c 100644 --- a/Documentation/nvme-device-self-test.txt +++ b/Documentation/nvme-device-self-test.txt @@ -24,7 +24,7 @@ OPTIONS ------- -n :: --namespace-id=:: - Indicate the namespace in which the device self-test has to becarried out + Indicate the namespace in which the device self-test has to be carried out -s :: --self-test-code=:: diff --git a/Documentation/nvme-dim.txt b/Documentation/nvme-dim.txt index 805c7ffe..52df256d 100644 --- a/Documentation/nvme-dim.txt +++ b/Documentation/nvme-dim.txt @@ -21,7 +21,7 @@ deregister. The DIM command is used to explicitly register with Discovery Controllers (DC), especially with Central Discovery Controllers (CDC). CDCs maintain a database (DB) -of all the Hosts and Storage Susbsystems in a network. The register task is used +of all the Hosts and Storage Subsystems in a network. The register task is used to add a host to the CDC's DB. The deregister task is used to remove a host from the CDC's DB. diff --git a/Documentation/nvme-discover.txt b/Documentation/nvme-discover.txt index e27949bf..53826d54 100644 --- a/Documentation/nvme-discover.txt +++ b/Documentation/nvme-discover.txt @@ -46,7 +46,7 @@ Discovery commands to run. If no @SYSCONFDIR@/nvme/discovery.conf file exists, the command will quit with an error. Otherwise, a specific Discovery Controller should be specified using the ---transport, --traddr, and if necessary the --trsvcid flags. A Diѕcovery +--transport, --traddr, and if necessary the --trsvcid flags. A Discovery request will then be sent to the specified Discovery Controller. BACKGROUND @@ -150,7 +150,7 @@ OPTIONS -k <#>:: --keep-alive-tmo=<#>:: - Overrides the default dealy (in seconds) for keep alive. + Overrides the default timeout (in seconds) for keep alive. This option will be ignored for the discovery, and it is only implemented for completeness. @@ -210,7 +210,7 @@ OPTIONS 'binary'. Only one output format can be used at a time. --force:: - Disable the built-in persitent discover connection rules. + Disable the built-in persistent discover connection rules. Combined with --persistent flag, always create new persistent discovery connection. diff --git a/Documentation/nvme-fid-support-effects-log.txt b/Documentation/nvme-fid-support-effects-log.txt index d2702eb2..5d12b18a 100644 --- a/Documentation/nvme-fid-support-effects-log.txt +++ b/Documentation/nvme-fid-support-effects-log.txt @@ -13,7 +13,7 @@ SYNOPSIS DESCRIPTION ----------- For the NVMe device given, sends an FID Support and Effects log and -provides the result and returned logstructure. +provides the result and returned log structure. The parameter is mandatory and may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1). diff --git a/Documentation/nvme-fw-commit.txt b/Documentation/nvme-fw-commit.txt index c164c5a2..337e783e 100644 --- a/Documentation/nvme-fw-commit.txt +++ b/Documentation/nvme-fw-commit.txt @@ -72,7 +72,7 @@ BPINFO.ABPID. --bpid=:: -b :: - Specifiies the Boot partition that shall be used for the Commit Action, + Specifies the Boot partition that shall be used for the Commit Action, if applicable (default: 0) EXAMPLES diff --git a/Documentation/nvme-fw-download.txt b/Documentation/nvme-fw-download.txt index 6b11d051..84e407ed 100644 --- a/Documentation/nvme-fw-download.txt +++ b/Documentation/nvme-fw-download.txt @@ -37,7 +37,7 @@ the Firmware Commit command (nvme fw-commit ). OPTIONS ------- -f :: ---fw=:: +--fw=:: Required argument. This specifies the path to the device's firmware file on your system that will be read by the program and sent to the device. diff --git a/Documentation/nvme-id-domain.txt b/Documentation/nvme-id-domain.txt index be7b81ab..87883c50 100644 --- a/Documentation/nvme-id-domain.txt +++ b/Documentation/nvme-id-domain.txt @@ -13,7 +13,7 @@ SYNOPSIS DESCRIPTION ----------- -For the NVMe device given, send an identify command and return the domian list +For the NVMe device given, send an identify command and return the domain list data structure. The parameter is mandatory and may be either the NVMe character diff --git a/Documentation/nvme-list-ns.txt b/Documentation/nvme-list-ns.txt index 0ccd1ada..753a9594 100644 --- a/Documentation/nvme-list-ns.txt +++ b/Documentation/nvme-list-ns.txt @@ -34,7 +34,7 @@ OPTIONS -y :: --csi=:: If this value is given, retrieve the identify list structure associated - with the speicified I/O command set. + with the specified I/O command set. -a:: --all:: diff --git a/Documentation/nvme-list.txt b/Documentation/nvme-list.txt index 22e00815..7cc333be 100644 --- a/Documentation/nvme-list.txt +++ b/Documentation/nvme-list.txt @@ -25,7 +25,7 @@ OPTIONS -v:: --verbose:: Increase the information in the output, showing nvme subsystems, - controllers and namespaces separately and how they're realted to each + controllers and namespaces separately and how they're related to each other. ENVIRONMENT diff --git a/Documentation/nvme-lockdown.txt b/Documentation/nvme-lockdown.txt index e9ba86c2..cf8a48ff 100644 --- a/Documentation/nvme-lockdown.txt +++ b/Documentation/nvme-lockdown.txt @@ -18,7 +18,7 @@ DESCRIPTION ----------- The Lockdown command is used to control the Command and Feature Lockdown capability which configures the prohibition or allowance of execution of the -specified commandor Set Features command targeting a specific Feature +specified command or Set Features command targeting a specific Feature Identifier. OPTIONS @@ -34,17 +34,17 @@ OPTIONS --prhbt=:: -p :: - Prohibit(PRHBT) bit specifies whether to prohibit or allow the command + Prohibit (PRHBT) bit specifies whether to prohibit or allow the command opcode or Set Features Feature Identifier specified by this command. --scp=:: -s :: - Scope(SCP) field specifies the contents of the Opcode or Feature Identifier field. + Scope (SCP) field specifies the contents of the Opcode or Feature Identifier field. --uuid=:: -U :: - UUID Index - If this field is set to a non-zerovalue, then the value of - this field is the index of a UUID in the UUIDList that is used by the command. + UUID Index - If this field is set to a non-zero value, then the value of + this field is the index of a UUID in the UUID List that is used by the command. If this field is cleared to 0h,then no UUID index is specified. EXAMPLES diff --git a/Documentation/nvme-micron-clear-pcie-errors.txt b/Documentation/nvme-micron-clear-pcie-errors.txt index d3afccfd..4df0e8a2 100644 --- a/Documentation/nvme-micron-clear-pcie-errors.txt +++ b/Documentation/nvme-micron-clear-pcie-errors.txt @@ -12,7 +12,7 @@ SYNOPSIS DESCRIPTION ----------- -This command clears corretable pcie errors for the specified Micron device. +This command clears correctable pcie errors for the specified Micron device. The parameter is mandatory and may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: diff --git a/Documentation/nvme-micron-internal-log.txt b/Documentation/nvme-micron-internal-log.txt index 66fb90fb..37a50ad4 100644 --- a/Documentation/nvme-micron-internal-log.txt +++ b/Documentation/nvme-micron-internal-log.txt @@ -13,8 +13,8 @@ SYNOPSIS DESCRIPTION ----------- For the given NVMe device, sends the Micron vendor specific device commands to retrieve -various logs (in binary format) and compresses them and saves into speficied zip file. -These vendor unique logs can be analysed with Micron Technical support team for any device +various logs (in binary format) and compresses them and saves into specified zip file. +These vendor unique logs can be analyzed with Micron Technical support team for any device specific issues The parameter is mandatory and may be either the NVMe diff --git a/Documentation/nvme-micron-temperature-stats.txt b/Documentation/nvme-micron-temperature-stats.txt index 43061c0e..8b013d9b 100644 --- a/Documentation/nvme-micron-temperature-stats.txt +++ b/Documentation/nvme-micron-temperature-stats.txt @@ -1,4 +1,4 @@ -nvme-micron-temperarature-stats(1) +nvme-micron-temperature-stats(1) ================================== NAME diff --git a/Documentation/nvme-pred-lat-event-agg-log.txt b/Documentation/nvme-pred-lat-event-agg-log.txt index d7d998b0..b01c9bb0 100644 --- a/Documentation/nvme-pred-lat-event-agg-log.txt +++ b/Documentation/nvme-pred-lat-event-agg-log.txt @@ -22,7 +22,7 @@ The parameter is mandatory and may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1). On success, the returned Predictable Latency Event Aggregate Log -Page structure may be returned in one ofseveral ways depending on +Page structure may be returned in one of several ways depending on the option flags; the structure may parsed by the program and printed in a readable format or the raw buffer may be printed to stdout for another program to parse. @@ -43,7 +43,7 @@ OPTIONS -b:: --raw-binary:: - Print the raw Predectible Latency Event Aggregate log buffer to stdout. + Print the raw Predictable Latency Event Aggregate log buffer to stdout. -o :: --output-format=:: @@ -59,7 +59,7 @@ EXAMPLES ------------ + -* Print the raw Predectible Latency Event Aggregate log to a file: +* Print the raw Predictable Latency Event Aggregate log to a file: + ------------ # nvme pred-lat-event-agg-log /dev/nvme0 --raw-binary > pred_lat_agg_log.raw diff --git a/Documentation/nvme-predictable-lat-log.txt b/Documentation/nvme-predictable-lat-log.txt index b4d7335b..d1dde80d 100644 --- a/Documentation/nvme-predictable-lat-log.txt +++ b/Documentation/nvme-predictable-lat-log.txt @@ -3,7 +3,7 @@ nvme-predictable-lat-log(1) NAME ---- -nvme-predictable-lat-log - Send Predectible latency per NVM set log page request, +nvme-predictable-lat-log - Send Predictable latency per NVM set log page request, returns result and log SYNOPSIS @@ -15,14 +15,14 @@ SYNOPSIS DESCRIPTION ----------- -Retrieves the NVMe Predectible latency per NVM set log page from an NVMe device +Retrieves the NVMe Predictable latency per NVM set log page from an NVMe device and provides the returned structure. The parameter is mandatory and may be either the NVMe character device (ex: /dev/nvme0), or a namespace block device (ex: /dev/nvme0n1). -On success, the returned Predectible latency per NVM set log structure -may be returned in one ofseveral ways depending on the option flags; the +On success, the returned Predictable latency per NVM set log structure +may be returned in one of several ways depending on the option flags; the structure may parsed by the program and printed in a readable format or the raw buffer may be printed to stdout for another program to parse. @@ -30,14 +30,14 @@ OPTIONS ------- -i :: --nvmset-id=:: - Retrieve the Predectible latency per NVM set log for the given nvmset id. + Retrieve the Predictable latency per NVM set log for the given nvmset id. This argument is mandatory and its success may depend on the device's statistics to provide this log For More details see NVM Express 1.4 Spec. Section 5.14.1.10. The default nvmset id to use is 1 for the device. -b:: --raw-binary:: - Print the raw Predectible latency per NVM set log buffer to stdout. + Print the raw Predictable latency per NVM set log buffer to stdout. -o :: --output-format=:: @@ -46,14 +46,14 @@ OPTIONS EXAMPLES -------- -* Print the Predectible latency per NVM set log page in a human readable format: +* Print the Predictable latency per NVM set log page in a human readable format: + ------------ # nvme predictable-lat-log /dev/nvme0 ------------ + -* Print the raw Predectible latency per NVM set log to a file: +* Print the raw Predictable latency per NVM set log to a file: + ------------ # nvme predictable-lat-log /dev/nvme0 --raw-binary > nvmset_log.raw diff --git a/Documentation/nvme-primary-ctrl-caps.txt b/Documentation/nvme-primary-ctrl-caps.txt index e17093f6..3edf5c1a 100644 --- a/Documentation/nvme-primary-ctrl-caps.txt +++ b/Documentation/nvme-primary-ctrl-caps.txt @@ -45,7 +45,7 @@ EXAMPLES fields in a human readable format: + ------------ -# nvme primary-ctrl-caps /dev/nvme0 --human-readbale +# nvme primary-ctrl-caps /dev/nvme0 --human-readable # nvme primary-ctrl-caps /dev/nvme0 -H ------------ NVME diff --git a/Documentation/nvme-read.txt b/Documentation/nvme-read.txt index 8565431c..c5f0e522 100644 --- a/Documentation/nvme-read.txt +++ b/Documentation/nvme-read.txt @@ -95,8 +95,8 @@ metadata is passes. --dir-type=:: Optional directive type. The nvme-cli only enforces the value be in the defined range for the directive type, though the NVMe - specifcation (1.3a) defines only one directive, 01h, for write - stream idenfiers. + specification (1.3a) defines only one directive, 01h, for write + stream identifiers. -S :: --dir-spec=:: @@ -136,7 +136,7 @@ metadata is passes. data protection processing. --force:: - Ignore namespace is currently busy and perfome the operation + Ignore namespace is currently busy and performed the operation even though. EXAMPLES diff --git a/Documentation/nvme-rpmb.txt b/Documentation/nvme-rpmb.txt index f9b371af..c30c83d8 100644 --- a/Documentation/nvme-rpmb.txt +++ b/Documentation/nvme-rpmb.txt @@ -41,7 +41,7 @@ OPTIONS RPMB target given with --target or -t options. As per spec, this is one time action which can't be undone. - read-couter - Read 'write counter' of specified RPMB target. The + read-counter - Read 'write counter' of specified RPMB target. The counter value read is printed onto STDOUT read-config - Read 512 bytes of device configuration block data of @@ -59,7 +59,7 @@ OPTIONS -o option should be given to read the amount of data to be read in 512 byte blocks. - write-data - Supports authenticated data writting to specified RPMB + write-data - Supports authenticated data writing to specified RPMB target (--target or -t option) at given offset specified with --address or -o option, using key specified using --keyfile or -k options. --blocks or @@ -99,10 +99,10 @@ OPTIONS -o :: --address=:: The address (in 512 byte sector offset from 0) to be used for data - trasnfer commands (read or write) for a specified RPMB target. + transfer commands (read or write) for a specified RPMB target. -b:: --blocks=:: - The size in 512 byte sectors to be used for data trasnfer commands + The size in 512 byte sectors to be used for data transfer commands (read or write) for a specified RPMB target. EXAMPLES @@ -113,7 +113,7 @@ EXAMPLES # nvme rpmb /dev/nvme0 --cmd=info ----------- + -* Program 'SecreteKey' as authentication key for target 1 +* Program 'SecretKey' as authentication key for target 1 + ------------ # nvme rpmb /dev/nvme0 --cmd=program-key -key='SecretKey' --target=1 @@ -134,7 +134,7 @@ EXAMPLES * Write 200 blocks of (512 bytes) from input.bin onto target 0 + ------------ -# nvme rpmb /dev/nvme0 -c write-data -t 0 -f input.bin -b 200 -k 'SecreteKey' +# nvme rpmb /dev/nvme0 -c write-data -t 0 -f input.bin -b 200 -k 'SecretKey' ------------ + * Read 200 blocks of (512 bytes) from target 2, at offset 0x100 and save the diff --git a/Documentation/nvme-sanitize.txt b/Documentation/nvme-sanitize.txt index be489d3f..196983b6 100644 --- a/Documentation/nvme-sanitize.txt +++ b/Documentation/nvme-sanitize.txt @@ -28,7 +28,7 @@ On success it returns 0, error code otherwise. OPTIONS ------- -d:: ---no-delloc:: +--no-dealloc:: No Deallocate After Sanitize: If set, then the controller shall not deallocate any logical blocks as a result of successfully completing the sanitize @@ -80,7 +80,7 @@ OPTIONS sanitize operation. --force:: - Ignore namespace is currently busy and perfome the operation + Ignore namespace is currently busy and performed the operation even though. EXAMPLES diff --git a/Documentation/nvme-self-test-log.txt b/Documentation/nvme-self-test-log.txt index a801cb09..56a3c4ac 100644 --- a/Documentation/nvme-self-test-log.txt +++ b/Documentation/nvme-self-test-log.txt @@ -3,7 +3,7 @@ nvme-self-test-log(1) NAME ---- -nvme-self-test-log - Retrieve the log information initited by device-self-test and display it +nvme-self-test-log - Retrieve the log information initiated by device-self-test and display it SYNOPSIS -------- diff --git a/Documentation/nvme-supported-log-pages.txt b/Documentation/nvme-supported-log-pages.txt index 3e9d37a9..32f95fec 100644 --- a/Documentation/nvme-supported-log-pages.txt +++ b/Documentation/nvme-supported-log-pages.txt @@ -13,13 +13,13 @@ SYNOPSIS DESCRIPTION ----------- -Retrieves the NVMe supportd log pages details from an NVMe device and provides +Retrieves the NVMe supported log pages details from an NVMe device and provides the returned structure. The parameter is mandatory and should be the NVMe character device (ex: /dev/nvme0). -On success, the returned supportd log pages log structure will be printed +On success, the returned supported log pages log structure will be printed for each command that is supported. OPTIONS diff --git a/Documentation/nvme-transcend-healthvalue.txt b/Documentation/nvme-transcend-healthvalue.txt index eecf68be..4a7d52f1 100644 --- a/Documentation/nvme-transcend-healthvalue.txt +++ b/Documentation/nvme-transcend-healthvalue.txt @@ -3,12 +3,12 @@ nvme-transcend-healthvalue(1) NAME ---- -nvme-transcend-healthvalue - Use NVMe SMART table to analyse the health value of Transcend device. +nvme-transcend-healthvalue - Use NVMe SMART table to analyze the health value of Transcend device. SYNOPSIS -------- [verse] -'nvme transcned healthvalue' +'nvme transcend healthvalue' DESCRIPTION ----------- @@ -29,7 +29,7 @@ EXAMPLES * Print the Transcend Device health value in a human readable format: + ------------ -# nvme transcned healthvalue /dev/nvme0 +# nvme transcend healthvalue /dev/nvme0 ------------ NVME diff --git a/Documentation/nvme-virtium-save-smart-to-vtview-log.txt b/Documentation/nvme-virtium-save-smart-to-vtview-log.txt index 3e27b7eb..313ac35a 100755 --- a/Documentation/nvme-virtium-save-smart-to-vtview-log.txt +++ b/Documentation/nvme-virtium-save-smart-to-vtview-log.txt @@ -38,7 +38,7 @@ of the log file name. OPTIONS ------- -r :: ---run-tim=:: +--run-time=:: (optional) Number of hours to log data (default = 20 hours) -f :: diff --git a/Documentation/nvme-wdc-get-drive-status.txt b/Documentation/nvme-wdc-get-drive-status.txt index f8a37d68..10e212b1 100644 --- a/Documentation/nvme-wdc-get-drive-status.txt +++ b/Documentation/nvme-wdc-get-drive-status.txt @@ -39,7 +39,7 @@ Output Explanation |The 2 possible states are : Present or Not Present. |*Thermal Throttling Status* -|The 3 possible states are : Off, On, or Unavaiable. +|The 3 possible states are : Off, On, or Unavailable. |*Format Corrupt Reason* |The 3 possible states are : Not Corrupted, Corrupt due to FW Assert, or Corrupt for Unknown Reason. diff --git a/Documentation/nvme-wdc-namespace-resize.txt b/Documentation/nvme-wdc-namespace-resize.txt index 288430f7..71fc7812 100644 --- a/Documentation/nvme-wdc-namespace-resize.txt +++ b/Documentation/nvme-wdc-namespace-resize.txt @@ -40,12 +40,12 @@ OPTIONS EXAMPLES -------- -* Resizes namespace 1 to 50% of the orginal TNVMCAP reported value: +* Resizes namespace 1 to 50% of the original TNVMCAP reported value: + ------------ # nvme wdc namespace-resize /dev/nvme0 -n 1 -o 3 ------------ -* Resizes namespace 2 to 7% of the orginal TNVMCAP reported value: +* Resizes namespace 2 to 7% of the original TNVMCAP reported value: + ------------ # nvme wdc namespace-resize /dev/nvme0 --namespace-id=2 --op-option=1 diff --git a/Documentation/nvme-wdc-vs-fw-activate-history.txt b/Documentation/nvme-wdc-vs-fw-activate-history.txt index 1ef20a6d..30c6edea 100644 --- a/Documentation/nvme-wdc-vs-fw-activate-history.txt +++ b/Documentation/nvme-wdc-vs-fw-activate-history.txt @@ -12,7 +12,7 @@ SYNOPSIS DESCRIPTION ----------- -For the NVMe device given, read a Vendor Unique WDC log page that returns the firmware actiation +For the NVMe device given, read a Vendor Unique WDC log page that returns the firmware activation history. The parameter is mandatory and must be the NVMe character device (ex: /dev/nvme0). @@ -53,13 +53,13 @@ Firmware Activate History Log Page Data Output Explanation |The new firmware level running on the SSD after the activation took place. |*Slot Number* -|The slot tht the firmware is being activated from. +|The slot that the firmware is being activated from. |*Commit Action Type* |The commit action type associated with the firmware activation event |*Result* -|The result of the firmware activation event. The ouput shall be in the format: +|The result of the firmware activation event. The output shall be in the format: Pass or Failed + error code |=== diff --git a/Documentation/nvme-write-uncor.txt b/Documentation/nvme-write-uncor.txt index 41a1d874..38af3136 100644 --- a/Documentation/nvme-write-uncor.txt +++ b/Documentation/nvme-write-uncor.txt @@ -8,7 +8,7 @@ nvme-write-uncor - Send an NVMe write uncorrectable command, return results SYNOPSIS -------- [verse] -'nvme-write-uncorr' [--start-block= | -s ] +'nvme-write-uncor' [--start-block= | -s ] [--block-count= | -c ] [--namespace-id= | -n ] [--force] @@ -33,7 +33,7 @@ OPTIONS Namespace ID use in the command. --force:: - Ignore namespace is currently busy and perfome the operation + Ignore namespace is currently busy and performed the operation even though. EXAMPLES diff --git a/Documentation/nvme-write-zeroes.txt b/Documentation/nvme-write-zeroes.txt index 764b5f87..cfcac36f 100644 --- a/Documentation/nvme-write-zeroes.txt +++ b/Documentation/nvme-write-zeroes.txt @@ -90,7 +90,7 @@ metadata is passes. data protection processing. --force:: - Ignore namespace is currently busy and perfome the operation + Ignore namespace is currently busy and performed the operation even though. EXAMPLES diff --git a/Documentation/nvme-write.txt b/Documentation/nvme-write.txt index 4ac46e03..837bd5ca 100644 --- a/Documentation/nvme-write.txt +++ b/Documentation/nvme-write.txt @@ -103,8 +103,8 @@ metadata is passes. --dir-type=:: Optional directive type. The nvme-cli only enforces the value be in the defined range for the directive type, though the NVMe - specifcation (1.3a) defines only one directive, 01h, for write - stream idenfiers. + specification (1.3a) defines only one directive, 01h, for write + stream identifiers. -S :: --dir-spec=:: @@ -144,7 +144,7 @@ metadata is passes. data protection processing. --force:: - Ignore namespace is currently busy and perfome the operation + Ignore namespace is currently busy and performed the operation even though. EXAMPLES diff --git a/Documentation/nvme-zns-id-ns.txt b/Documentation/nvme-zns-id-ns.txt index dccb02cf..799e3b67 100644 --- a/Documentation/nvme-zns-id-ns.txt +++ b/Documentation/nvme-zns-id-ns.txt @@ -15,7 +15,7 @@ SYNOPSIS DESCRIPTION ----------- -For the NVMe device given, sends the zoned command set's identify namepsace +For the NVMe device given, sends the zoned command set's identify namespace command and provides the result and returned structure. The parameter is mandatory and may be either the NVMe character diff --git a/Documentation/nvme-zns-set-zone-desc.txt b/Documentation/nvme-zns-set-zone-desc.txt index ca598b85..dd759a21 100644 --- a/Documentation/nvme-zns-set-zone-desc.txt +++ b/Documentation/nvme-zns-set-zone-desc.txt @@ -8,7 +8,7 @@ nvme-zns-set-zone-desc - Set extended descriptor data for a zone SYNOPSIS -------- [verse] -'nvme zns setzone-desc' [--namespace-id= | -n ] +'nvme zns set-zone-desc' [--namespace-id= | -n ] [--start-lba=, -s ] [--zrwaa | -r] [-data=, -d ] @@ -17,9 +17,9 @@ SYNOPSIS DESCRIPTION ----------- For the NVMe device given, issues the Zone Management Send command with the -Set Zone Descriptor Extenions action. The input will default to stdin. +Set Zone Descriptor Extensions action. The input will default to stdin. Alternatively, the data may come from a file that can be specified. The data -length will automatically be calculated from the zns identify namesapce. +length will automatically be calculated from the zns identify namespace. OPTIONS ------- diff --git a/Documentation/nvme-zns-zone-append.txt b/Documentation/nvme-zns-zone-append.txt index 37242a54..65e0fb23 100644 --- a/Documentation/nvme-zns-zone-append.txt +++ b/Documentation/nvme-zns-zone-append.txt @@ -27,7 +27,7 @@ The zone append command writes the logical blocks specified by the command to the medium from the data data buffer provided. Will use stdin by default if you don't provide a file. -On sucess, the program will report the LBA that was assigned to the data for +On success, the program will report the LBA that was assigned to the data for the append operation. OPTIONS diff --git a/Documentation/nvme-zns-zrwa-flush-zone.txt b/Documentation/nvme-zns-zrwa-flush-zone.txt index 19e79263..4f3e72ca 100644 --- a/Documentation/nvme-zns-zrwa-flush-zone.txt +++ b/Documentation/nvme-zns-zrwa-flush-zone.txt @@ -39,7 +39,7 @@ OPTIONS EXAMPLES -------- -* flush the first zwra of first zone for zrwacg(15) on namespace 1: +* flush the first zrwa of first zone for zrwacg(15) on namespace 1: + ------------ # nvme zns zrwa-flush-zone /dev/nvme0 -n 1 -l 15