Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions README
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ CONFIG FILES
Then when you run "linux_logo" it will automatically show an ASCII classic
logo with the formatting command applied.

This is a bit ugly, but is was simpler and [at the time] seemed more elegant
This is a bit ugly, but it was simpler and [at the time] seemed more elegant
than writing a separate dot file parser....

----------------------------------------------------------------------->
Expand Down Expand Up @@ -365,7 +365,7 @@ Notes:
+ The letter after the # must be capitalized.
+ Options not available are silently ignored.
+ Megahertz only available on some platforms and newer kernels.
+ See "defaults.h" on how to have #N report in non-english numbers.
+ See "defaults.h" on how to have #N report in non-English numbers.
+ Plural [#S] gives nothing if there is 1 cpu, gives 's' otherwise.
+ Processor [#P] gives "Processor" [or i18n equiv] when 1 cpu,
"Processors" if more than 1.
Expand Down
4 changes: 2 additions & 2 deletions README.CUSTOM_LOGOS
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ Creating custom logo files:
A classic logo is usually a picture 22 wide by 16 high, with
the OS name printed in block letters to the right of the first
6 lines. The system information is then printed starting on
line 8 and until the sysinfo runs out [typicall between 5-8 lines].
line 8 and until the sysinfo runs out [typically between 5-8 lines].

BEGIN_ASCII_LOGO
END_ASCII_LOGO
Expand All @@ -120,7 +120,7 @@ Creating custom logo files:
+ Be sure to remember to end your directives, and not to nest logo
directives. I have not tested the parser to see how robust it is.

+ Be sure to have both a LOGO and a ASCII_LOGO in the logo file
+ Be sure to have both a LOGO and an ASCII_LOGO in the logo file
if not, parse_logo will not be able to add them (core dump :(
You might use the script in contrib/script/logo2ascii in order to
convert them.
Expand Down
2 changes: 1 addition & 1 deletion README.history
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ It was a complete overhaul of the code, to sort out a lot of issues
where my C coding had gotten better, and to also fix a lot of stupid
decisions made earlier.

linux_logo was in maintenence mode for a long time, but eventually
linux_logo was in maintenance mode for a long time, but eventually
made some changes to fix logo selection, and to make it easier
to configure from the command line (that is, make it a more UNIX-like
tool). I initially wasn't planning on a new major number, but in the
Expand Down