1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/hwmon/abituguru-datasheet b/Documentation/hwmon/abituguru-datasheet
index d9251efdcec7..8d2be8a0b1e3 100644
--- a/Documentation/hwmon/abituguru-datasheet
+++ b/Documentation/hwmon/abituguru-datasheet
@@ -5,9 +5,9 @@ First of all, what I know about uGuru is no fact based on any help, hints or
 datasheet from Abit. The data I have got on uGuru have I assembled through
 my weak knowledge in "backwards engineering".
 And just for the record, you may have noticed uGuru isn't a chip developed by
-Abit, as they claim it to be. It's realy just an microprocessor (uC) created by
+Abit, as they claim it to be. It's really just an microprocessor (uC) created by
 Winbond (W83L950D). And no, reading the manual for this specific uC or
-mailing  Windbond for help won't give any usefull data about uGuru, as it is
+mailing  Windbond for help won't give any useful data about uGuru, as it is
 the program inside the uC that is responding to calls.
 Olle Sandberg <ollebull@gmail.com>, 2005-05-25
@@ -41,7 +41,7 @@ later on attached again data-port will hold 0x08, more about this later.
 After wider testing of the Linux kernel driver some variants of the uGuru have
 turned up which will hold 0x00 instead of 0xAC at the CMD port, thus we also
-have to test CMD for two different values. On these uGuru's DATA will initally
+have to test CMD for two different values. On these uGuru's DATA will initially
 hold 0x09 and will only hold 0x08 after reading CMD first, so CMD must be read
 first!
@@ -308,5 +308,5 @@ the voltage / clock programming out, I tried reading and only reading banks
 resulted in a _permanent_ reprogramming of the voltages, luckily I had the
 sensors part configured so that it would shutdown my system on any out of spec
 voltages which proprably safed my computer (after a reboot I managed to
-immediatly enter the bios and reload the defaults). This probably means that
+immediately enter the bios and reload the defaults). This probably means that
 the read/write cycle for the non sensor part is different from the sensor part.

diff --git a/Documentation/hwmon/abituguru-datasheet b/Documentation/hwmon/abituguru-datasheet index d9251efdcec7..8d2be8a0b1e3 100644 --- a/Documentation/hwmon/abituguru-datasheet +++ b/Documentation/hwmon/abituguru-datasheet
@@ -5,9 +5,9 @@ First of all, what I know about uGuru is no fact based on any help, hints or
5	datasheet from Abit. The data I have got on uGuru have I assembled through	5	datasheet from Abit. The data I have got on uGuru have I assembled through
6	my weak knowledge in "backwards engineering".	6	my weak knowledge in "backwards engineering".
7	And just for the record, you may have noticed uGuru isn't a chip developed by	7	And just for the record, you may have noticed uGuru isn't a chip developed by
8	Abit, as they claim it to be. It's realy just an microprocessor (uC) created by	8	Abit, as they claim it to be. It's really just an microprocessor (uC) created by
9	Winbond (W83L950D). And no, reading the manual for this specific uC or	9	Winbond (W83L950D). And no, reading the manual for this specific uC or
10	mailing Windbond for help won't give any usefull data about uGuru, as it is	10	mailing Windbond for help won't give any useful data about uGuru, as it is
11	the program inside the uC that is responding to calls.	11	the program inside the uC that is responding to calls.
12		12
13	Olle Sandberg <ollebull@gmail.com>, 2005-05-25	13	Olle Sandberg <ollebull@gmail.com>, 2005-05-25
@@ -41,7 +41,7 @@ later on attached again data-port will hold 0x08, more about this later.
41		41
42	After wider testing of the Linux kernel driver some variants of the uGuru have	42	After wider testing of the Linux kernel driver some variants of the uGuru have
43	turned up which will hold 0x00 instead of 0xAC at the CMD port, thus we also	43	turned up which will hold 0x00 instead of 0xAC at the CMD port, thus we also
44	have to test CMD for two different values. On these uGuru's DATA will initally	44	have to test CMD for two different values. On these uGuru's DATA will initially
45	hold 0x09 and will only hold 0x08 after reading CMD first, so CMD must be read	45	hold 0x09 and will only hold 0x08 after reading CMD first, so CMD must be read
46	first!	46	first!
47		47
@@ -308,5 +308,5 @@ the voltage / clock programming out, I tried reading and only reading banks
308	resulted in a _permanent_ reprogramming of the voltages, luckily I had the	308	resulted in a _permanent_ reprogramming of the voltages, luckily I had the
309	sensors part configured so that it would shutdown my system on any out of spec	309	sensors part configured so that it would shutdown my system on any out of spec
310	voltages which proprably safed my computer (after a reboot I managed to	310	voltages which proprably safed my computer (after a reboot I managed to
311	immediatly enter the bios and reload the defaults). This probably means that	311	immediately enter the bios and reload the defaults). This probably means that
312	the read/write cycle for the non sensor part is different from the sensor part.	312	the read/write cycle for the non sensor part is different from the sensor part.