fix spelling

This commit is contained in:
a1346054 2021-08-25 02:13:54 +00:00
parent d6b01b07b1
commit e09ec42630
3 changed files with 10 additions and 10 deletions

View file

@ -107,7 +107,7 @@ wget -O inxi https://smxi.org/inxi
wget -O inxi smxi.org/inxi wget -O inxi smxi.org/inxi
NOTE: Just because github calls tagged commits 'Releases' does not mean they are NOTE: Just because github calls tagged commits 'Releases' does not mean they are
releases! I can't change the words on the tag page. They are tagged commmits, releases! I can't change the words on the tag page. They are tagged commits,
period. A tag is a pointer to a commit, and has no further meaning. period. A tag is a pointer to a commit, and has no further meaning.
If your distribution has blocked -U self updater and you want a newer version: If your distribution has blocked -U self updater and you want a newer version:

8
inxi
View file

@ -121,7 +121,7 @@ my $line1 = "-------------------------------------------------------------------
my $line2 = "======================================================================\n"; my $line2 = "======================================================================\n";
my $line3 = "----------------------------------------\n"; my $line3 = "----------------------------------------\n";
my ($output_file,$output_type) = ('','screen'); my ($output_file,$output_type) = ('','screen');
my $prefix = 0; # for the primiary row hash key prefix my $prefix = 0; # for the primary row hash key prefix
## Initialize internal hashes ## Initialize internal hashes
# these assign a separator to non irc states. Important! Using ':' can # these assign a separator to non irc states. Important! Using ':' can
@ -14093,7 +14093,7 @@ sub get {
push(@rows,device_output()); push(@rows,device_output());
} }
push(@rows,usb_output()); push(@rows,usb_output());
# note: rasberry pi uses usb networking only # note: raspberry pi uses usb networking only
if (!@rows){ if (!@rows){
if ($b_arm || $b_mips){ if ($b_arm || $b_mips){
my $type = ($b_arm) ? 'arm' : 'mips'; my $type = ($b_arm) ? 'arm' : 'mips';
@ -23317,7 +23317,7 @@ sub get_linux_distro {
$distro_id = $1; $distro_id = $1;
$b_skip_issue = 1; $b_skip_issue = 1;
} }
# this raspbian detection fails for rasberry pi os # this raspbian detection fails for raspberry pi os
elsif ($lc_issue =~ /(raspbian|peppermint)/){ elsif ($lc_issue =~ /(raspbian|peppermint)/){
$distro_id = $1; $distro_id = $1;
$distro_file = $os_release if @osr; $distro_file = $os_release if @osr;
@ -24673,7 +24673,7 @@ sub bsd_data {
eval $end if $b_log; eval $end if $b_log;
return $memory; return $memory;
} }
# rasberry pi only # raspberry pi only
sub gpu_ram_arm { sub gpu_ram_arm {
eval $start if $b_log; eval $start if $b_log;
my ($gpu_ram) = (0); my ($gpu_ram) = (0);

10
inxi.1
View file

@ -328,7 +328,7 @@ for extra information (init type/version, runlevel, packages).
Note: if \fB\-m\fR is used or triggered, the memory item will show in the main Note: if \fB\-m\fR is used or triggered, the memory item will show in the main
Memory: report of \fB\-m\fR, not in \fB\Info:\fR. Memory: report of \fB\-m\fR, not in \fB\Info:\fR.
Rasberry Pi only: uses \fBvcgencmd get_mem gpu\fR to get gpu RAM amount, Raspberry Pi only: uses \fBvcgencmd get_mem gpu\fR to get gpu RAM amount,
if user is in video group and \fBvcgencmd\fR is installed. Uses if user is in video group and \fBvcgencmd\fR is installed. Uses
this result to increase the \fBMemory:\fR amount and \fBused:\fR amounts. this result to increase the \fBMemory:\fR amount and \fBused:\fR amounts.
@ -1069,7 +1069,7 @@ specific vendor [product] information.
.TP .TP
.B \-x \-o\fR, \fB\-x \-p\fR, \fB\-x \-P\fR .B \-x \-o\fR, \fB\-x \-p\fR, \fB\-x \-P\fR
\- Adds \fBmapper:\fR (the \fB/dev/mapper/\fR partitioni ID) \- Adds \fBmapper:\fR (the \fB/dev/mapper/\fR partition ID)
if mapped partition. if mapped partition.
Example: \fBID\-4: /home ... dev: /dev/dm-6 mapped: ar0-home\fR Example: \fBID\-4: /home ... dev: /dev/dm-6 mapped: ar0-home\fR
@ -1309,7 +1309,7 @@ Currently not able to detect all schemes, but handles the most common, e.g.
cases), e.g. \fBtype: HDD rpm: 7200\fR, or \fBtype: SSD\fR if positive SSD cases), e.g. \fBtype: HDD rpm: 7200\fR, or \fBtype: SSD\fR if positive SSD
identification was made. If no HDD, rotation, or positive SSD ID found, shows identification was made. If no HDD, rotation, or positive SSD ID found, shows
\fBtype: N/A\fR. Not all HDD spinning disks report their speed, so even if they \fBtype: N/A\fR. Not all HDD spinning disks report their speed, so even if they
are spinnning, no rpm data will show. are spinning, no rpm data will show.
.TP .TP
.B \-xxx \-E\fR (\fB\-\-bluetooth\fR) .B \-xxx \-E\fR (\fB\-\-bluetooth\fR)
@ -1915,7 +1915,7 @@ Use only the (comma separated) sensor arrays for \fB\-s\fR output. Make
permanent with \fBSENSORS_USE\fR configuration item. Sensor array ID value permanent with \fBSENSORS_USE\fR configuration item. Sensor array ID value
must be the exact value shown in lm\-sensors sensors output (Linux/lm-sensors must be the exact value shown in lm\-sensors sensors output (Linux/lm-sensors
only). If you only want to exclude one (or more) sensors from the output, only). If you only want to exclude one (or more) sensors from the output,
use \fB\-\-sensors\-exlude\fR. use \fB\-\-sensors\-exclude\fR.
Can be useful if the default sensor data used by inxi is not from the right Can be useful if the default sensor data used by inxi is not from the right
sensor array. Note that all other sensor data will be removed, which may lead sensor array. Note that all other sensor data will be removed, which may lead
@ -1927,7 +1927,7 @@ another one.
Most likely best use is when one (or two) of the sensor arrays has all the Most likely best use is when one (or two) of the sensor arrays has all the
sensor data you want, and you just want to make sure inxi doesn't use data sensor data you want, and you just want to make sure inxi doesn't use data
from another array that has inacurate or misleading data. from another array that has inaccurate or misleading data.
Note that gpu, network, disk, and other specific device monitor chips are Note that gpu, network, disk, and other specific device monitor chips are
excluded by default, and should not be added since they do not provide cpu, excluded by default, and should not be added since they do not provide cpu,