README*: Grammatical cleanups

Conflicts:
	AUTHORS
	README

AUTHORS

@@ -41,3 +41,4 @@ pontus <liquidpontus@yahoo.se>
 Tydus <Tydus@Tydus.org>
 Raulo <p987341@gmail.com>
 Thorsten Gilling <tgilling@web.de>
+Red_Wolf_2 <redwolf@wolfnexus.net>

README

@@ -39,12 +39,12 @@ MORE INFORMATION ON EACH.
 EXECUTIVE SUMMARY ON USAGE:
 
 After saving configuration from the menu, you do not need to give BFGMiner any
-arguments and it will load your configuration.
+arguments, it will load your configuration instead.
 
 Any configuration file may also contain a single
 	"include" : "filename"
 to recursively include another configuration file.
-Writing the configuration will save all settings from all files in the output.
+Writing the configuration will save all settings from all files to the output
 
 
 Single pool:
@@ -103,7 +103,7 @@ Optional Dependencies:
 	  libpdcurses        http://pdcurses.sourceforge.net/ (Linux/Mac/Windows)
 
 	Multiple ASIC/FPGA autodetection: any one of:
-	  sysfs              (builtin to most Linux kernels, just mount on /sys)
+	  sysfs              (built-in to most Linux kernels, just mount on /sys)
 	  libudev-dev        http://www.freedesktop.org/software/systemd/libudev/
 	
 	HashBuster & NanoFury USB devices:
@@ -223,7 +223,7 @@ Options for both config file and command line:
 --log-file|-L <arg> Append log file for output messages
 --log-microseconds  Include microseconds in log output
 --monitor|-m <arg>  Use custom pipe cmd for output messages
---net-delay         Impose small delays in networking to not overload slow routers
+--net-delay         Impose small delays in networking to avoid overloading slow routers
 --no-gbt            Disable getblocktemplate support
 --no-getwork        Disable getwork support
 --no-longpoll       Disable X-Long-Polling support
@@ -418,7 +418,7 @@ co[M]pact: off
 Q quits the application.
 
 
-The running log shows output like this:
+The running log shows output similar to that below:
 
  [2013-02-13 00:26:30] Accepted 1758e8df BFL 0  pool 0 Diff 10/1
  [2013-02-13 00:26:32] Accepted 1d9a2199 MMQ 0a pool 0 Diff 8/1
@@ -516,7 +516,8 @@ between the rest of the pools.
 
 BALANCE:
 This strategy monitors the amount of difficulty 1 shares solved for each pool
-and uses it to try to end up doing the same amount of work for all pools.
+and uses it as a basis for trying to doing the same amount of work for each
+pool.
 
 
 ---
@@ -657,9 +658,9 @@ FAQ
 
 Q: Why can't BFGMiner find lib<something> even after I installed it from source
 code?
-A: On UNIX-like operating systems, you often need to run some command to reload
-its library caches such as "ldconfig" or similar. A couple of systems (such as
-Fedora) ship with /usr/local/lib missing from their library search path. In
+A: On UNIX-like operating systems, you often need to run one or more commands to
+reload library caches, such as "ldconfig" or similar. A couple of systems (such
+as Fedora) ship with /usr/local/lib missing from their library search path. In
 this case, you can usually add it like this:
     echo /usr/local/lib >/etc/ld.so.conf.d/local.conf
 Please note that if your libraries installed into lib64 instead of lib, you
@@ -677,7 +678,7 @@ make it invalidate the work from each other.
 
 Q: Can I configure BFGMiner to mine with different login credentials or pools
 for each separate device?
-A: No.
+A: No such feature has been implemented to support this.
 
 Q: Can I put multiple pools in the config file?
 A: Yes, check the example.conf file. Alternatively, set up everything either on
@@ -701,17 +702,18 @@ useful and not risk idle periods. You can disable this behaviour with the
 option --failover-only.
 
 Q: Is this a virus?
-A: BFGMiner is being packaged with other trojan scripts and some antivirus
-software is falsely accusing bfgminer.exe as being the actual virus, rather
-than whatever it is being packaged with. If you installed BFGMiner yourself,
-then you do not have a virus on your computer. Complain to your antivirus
-software company. They seem to be flagging even source code now from BFGMiner
-as viruses, even though text source files can't do anything by themself.
+A: As BFGMiner is being packaged with other trojan scripts, some antivirus
+software is falsely accusing bfgminer.exe as being the actual virus, rather than
+whatever it is being packaged with. If you installed BFGMiner yourself from a
+reputable source then you do not have a virus on your computer. Complain to your
+antivirus software company. They seem to be flagging even source code from
+BFGMiner as malicious now, even though text source files can't do anything by
+themselves.
 
 Q: Can you modify the display to include more of one thing in the output and
 less of another, or can you change the quiet mode or can you add yet another
 output mode?
-A: Everyone will always have their own view of what's important to monitor.
+A: Everyone will always have their own view of what is important to monitor.
 The defaults are very sane and I have very little interest in changing this
 any further.
 
@@ -719,7 +721,7 @@ Q: Why is my efficiency above/below 1.00?
 A: Efficiency simply means how many shares you return for the amount of
 bandwidth used. It does not correlate with efficient use of your hardware, and
 is a measure of a combination of hardware speed, block luck, pool design and
-other factors.
+many other factors.
 
 Q: What are the best parameters to pass for X pool/hardware/device.
 A: Virtually always, the DEFAULT parameters give the best results. Most user
@@ -734,22 +736,22 @@ released for Windows but CPU mining can be built into BFGMiner when it is
 compiled. For builds which do support CPU mining, it is still disabled by
 default, and must be enabled using the -S cpu:auto option.
 
-Q: GUI version?
-A: No. The RPC interface makes it possible for someone else to write one
-though.
+Q: Will there ever be a GUI version?
+A: No, however the RPC interface makes it possible for someone else to write one
+if they choose.
 
 Q: I'm having an issue. What debugging information should I provide?
 A: Start BFGMiner with your regular commands and add -D -T --verbose and provide
-the full startup output and a summary of your hardware, operating system, ATI
-driver version and ATI stream version.
+the full startup output and a summary of your hardware, operating system, and if
+applicable, ATI driver version and ATI stream version.
 
 Q: Can I mine with BFGMiner on a Mac?
 A: BFGMiner will compile on OS X, but the performance of GPU mining is
 compromised due to the OpenCL implementation on OS X, there is no temperature or
-fanspeed monitoring, and the cooling design of most Macs, despite having
+fanspeed monitoring and the cooling design of most Macs, despite having
 powerful GPUs, will usually not cope with constant usage leading to a high risk
-of thermal damage. It is highly recommended not to mine on a Mac unless it is to
-a USB device.
+of thermal damage. It is highly recommended not to mine on a Mac unless it is
+with an external USB device.
 
 Q: My network gets slower and slower and then dies for a minute?
 A; Try the --net-delay option.
@@ -768,7 +770,7 @@ will not work.
 Q: I run PHP on windows to access the API with the example miner.php. Why does
 it fail when php is installed properly but I only get errors about Sockets not
 working in the logs?
-A: http://us.php.net/manual/en/sockets.installation.php
+A: Please check http://us.php.net/manual/en/sockets.installation.php
 
 Q: What is a PGA?
 A: At the moment, BFGMiner supports 5 FPGAs: BitForce, Icarus, ModMiner, X6500,
@@ -808,19 +810,20 @@ using Zadig). Before you can use BFGMiner, you will need to restore the original
 driver. With Linux, usually rebooting or re-plugging the device is sufficient.
 
 Q: On Linux I can see the /dev/ttyUSB* devices for my ICA/BFL/MMQ FPGA, but
-BFGMiner can't mine on them
-A: Make sure you have the required priviledges to access the /dev/ttyUSB*
+BFGMiner can't mine on them?
+A: Make sure you have the required privileges to access the /dev/ttyUSB*
 devices:
  sudo ls -las /dev/ttyUSB*
 will give output like:
  0 crw-rw---- 1 root dialout 188, 0 2012-09-11 13:49 /dev/ttyUSB0
-This means your account must have the group 'dialout' or root priviledges
+This means your account must have the group 'dialout' or root privileges
 To permanently give your account the 'dialout' group:
  sudo usermod -G dialout -a `whoami`
 Then logout and back in again
 
 Q: Can I mine scrypt with FPGAs or ASICs?
-A: No.
+A: Currently no. Bitcoin ASICs are only useful for SHA256d systems and FPGAs
+generally aren't designed to handle scrypt efficiently.
 
 Q: Why does BFGMiner show difficulty 0 when mining scrypt?
 A: BFGMiner consistently uses pdiff measurement for difficulty everywhere,
@@ -847,8 +850,9 @@ A: As an example, if you look at 'Difficulty Accepted' in the RPC API, the numbe
 of difficulty shares accepted does not usually exactly equal the amount of work
 done to find them. If you are mining at 8 difficulty, then you would expect on
 average to find one 8 difficulty share, per 8 single difficulty shares found.
-However, the number is actually random and converges over time, it is an average,
-not an exact value, thus you may find more or less than the expected average.
+However, the number is actually random and converges over time as it is an
+average, not an exact value, thus you may find more or less than the expected
+average.
 
 ---
 

README.ASIC

@@ -26,7 +26,7 @@ router used by the Avalon. eg:
 The values are baud : miners : asic count : timeout : frequency.
 
 Baud:
-The device is pretty much hard coded to emulate 115200 baud so you shouldn't
+The device is essentially hard coded to emulate 115200 baud so you shouldn't
 change this.
 
 Miners:
@@ -37,8 +37,9 @@ Asic count:
 Virtually all have 10, so don't change this.
 
 Timeout:
-This is how long the device will work on a work item before accepting new work
-to replace it. It should be changed according to the frequency (last setting).
+This defines how long the device will work on a work item before accepting new
+work to replace it. It should be changed according to the frequency (last
+setting).
 It is possible to set this a little lower if you are trying to tune for short
 block mining (eg p2pool) but much lower and the device will start creating
 duplicate shares.
@@ -63,7 +64,7 @@ AVA 0: 22/ 46C  60%/2400R
 The values are:
 ambient temp / highest device temp  set fan % / lowest detected fan RPM.
 
-Use the API for more detailed information than this.
+Check the API for more detailed information.
 
 
 BFSB, MEGABIGPOWER, AND METABANK BITFURY BOARDS

README.FPGA

@@ -15,27 +15,27 @@ from FPGA Mining LLC's website:
 -
 
 If the MMQ doesn't respond to BFGMiner at all, or the red LED isn't flashing
-then you will need to reset the MMQ
+then you will need to reset the MMQ.
 
-The red LED should always be flashing when it is mining or ready to mine
+The red LED should always be flashing when it is mining or ready to mine.
 
 To reset the MMQ, you are best to press the left "RESET" button on the
-backplane, then unplug and replug the USB cable
+backplane, then unplug and replug the USB cable.
 
 If your MMQ doesn't have a button on the "RESET" pad, you need to join the two
 left pads of the "RESET" pad with conductive wire to reset it. Cutting a small
-(metal) paper-clip in half works well for this
+(metal) paper-clip in half works well for this.
 
-Then unplug the USB cable, wait for 5 seconds, then plug it back in
+Then unplug the USB cable, wait for 5 seconds, then plug it back in.
 
-After you press reset, the red LED near the USB port should blink continuously
+After you press reset, the red LED near the USB port should blink continuously.
 
 If it still wont work, power off, wait for 5 seconds, then power on the MMQ
-This of course means it will upload the bitstream again when you start BFGMiner
+This of course means it will upload the bitstream again when you start BFGMiner.
 
 -
 
-Device 0 is on the power end of the board
+Device 0 is on the power end of the board.
 
 -
 
@@ -45,25 +45,25 @@ Read here for official details of changing the firmware:
 
 The basics of changing the firmware are:
  You need two short pieces of conductive wire if your MMQ doesn't have buttons
- on the "RESET" and "ISP" pads on the backplane board
- Cutting a small (metal) paper-clip in half works well for this
+ on the "RESET" and "ISP" pads on the backplane board.
+ Cutting a small (metal) paper-clip in half works well for this.
 
- Join the 2 left pads of the "RESET" pad with wire and the led will dim
+ Join the 2 left pads of the "RESET" pad with wire and the led will dim.
  Without disconnecting the "RESET", join the 2 left pads of the "ISP" pad with
- a wire and it will stay dim
- Release "RESET" then release "ISP" and is should still be dim
+ a wire and it will stay dim.
+ Release "RESET" then release "ISP" and is should still be dim.
  Unplug the USB and when you plug it back in it will show up as a mass storage
- device
+ device.
   Linux: (as one single line):
    mcopy -i /dev/disk/by-id/usb-NXP_LPC134X_IFLASH_ISP000000000-0:0
       modminer091012.bin ::/firmware.bin
   Windows: delete the MSD device file firmware.bin and copy in the new one
    rename the new file and put it under the same name 'firmware.bin'
  Disconnect the USB correctly (so writes are flushed first)
- Join and then disconnect "RESET" and then plug the USB back in and it's done
+ Join and then disconnect "RESET" and then plug the USB back in and it's done.
 
 Best to update to one of the latest 2 listed below if you don't already
-have one of them in your MMQ
+have one of them in your MMQ.
 
 The current latest different firmware are:
 
@@ -74,27 +74,27 @@ The current latest different firmware are:
   http://btcfpga.com/files/firmware/modminer091012.bin
 
 The code is currently tested on the modminer091012.bin firmware.
-This comment will be updated when others have been tested
+This comment will be updated when others have been tested.
 
 -
 
 On many Linux distributions there is an app called modem-manager that may cause
-problems when it is enabled, due to opening the MMQ device and writing to it
+problems when it is enabled, due to opening the MMQ device and writing to it.
 
 The problem will typically present itself by the flashing led on the backplane
 going out (no longer flashing) and it takes a power cycle to re-enable the MMQ
-firmware - which then can lead to the problem happening again
+firmware - which then can lead to the problem reoccurring.
 
 You can either disable/uninstall modem-manager if you don't need it or:
 a (hack) solution to this is to blacklist the MMQ USB device in
 /lib/udev/rules.d/77-mm-usb-device-blacklist.rules
 
-Adding 2 lines like this (just above APC) should help
+Adding 2 lines like this (just above APC) should help.
 # MMQ
 ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="0003", ENV{ID_MM_DEVICE_IGNORE}="1"
 
 The change will be lost and need to be re-done, next time you update the
-modem-manager software
+modem-manager software.
 
 
 BitForce (BFL)
@@ -121,7 +121,7 @@ To flash your BFL, specify the BFL port and the flash file e.g.:
  sudo ./bitforce-firmware-flash /dev/ttyUSB0 alphaminer_832.bfl
 It takes a bit under 3 minutes to flash a BFL and shows a progress % counter
 Once it completes, you may also need to wait about 15 seconds, then power the
-BFL off and on again
+BFL off and on again.
 
 If you get an error at the end of the BFL flash process stating:
  "Error reading response from ZBX"
@@ -153,12 +153,12 @@ There are two hidden options in BFGMiner when Icarus support is compiled in:
                                (enabled by default)
 
 If you define fewer comma separated values than Icarus devices, the last values
-will be used for all extra devices
+will be used for all extra devices.
 
 An example would be: --icarus-options 57600:2:1:-r
 This would mean: use 57600 baud, the FPGA board divides the work in half however
 only 1 FPGA actually runs on the board, and don't reopen the device (e.g. like
-an early CM1 Icarus copy bitstream)
+an early CM1 Icarus copy bitstream).
 
 --icarus-timing <arg> Set how the Icarus timing is calculated - one setting/value for all or comma separated
            default[=N]   Use the default Icarus hash time (2.6316ns)
@@ -167,63 +167,62 @@ an early CM1 Icarus copy bitstream)
            value[=N]     Specify the hash time in nanoseconds (e.g. 2.6316) and abort time (e.g. 2.6316=80)
 
 If you define fewer comma separated values than Icarus devices, the last values
-will be used for all extra devices
+will be used for all extra devices.
 
 Icarus timing is required for devices that do not exactly match a default
-Icarus Rev3 in processing speed
+Icarus Rev3 in processing speed.
 If you have an Icarus Rev3 you should not normally need to use --icarus-timing
-since the default values will maximise the Mh/s and display it correctly
+since the default values will maximise the Mh/s and display it correctly.
 
 Icarus timing is used to determine the number of hashes that have been checked
-when it aborts a nonce range (including on a longpoll)
+when it aborts a nonce range (including on a longpoll).
 It is also used to determine the elapsed time when it should abort a nonce
 range to avoid letting the Icarus go idle, but also to safely maximise that
-time
+time.
 
 'short' or 'long' mode should only be used on a computer that has enough CPU
 available to run BFGMiner without any CPU delays (an active desktop or swapping
-computer would not be stable enough)
+computer would not be stable enough).
 Any CPU delays while calculating the hash time will affect the result
 'short' mode only requires the computer to be stable until it has completed
-~315 difficulty 1 shares
-'long' mode requires it to always be stable to ensure accuracy, however, over
-time it continually corrects itself
+~315 difficulty 1 shares, 'long' mode requires it to always be stable to ensure
+accuracy, however, over time it continually corrects itself.
 The optional additional =N for 'short' or 'long' specifies the limit to set the
 timeout to in deciseconds; thus if the timing code calculation is higher while
-running, it will instead use the limit
+running, it will instead use the limit.
 This can be set to the appropriate value to ensure the device never goes idle
-even if the calculation is negatively affected by system performance
+even if the calculation is negatively affected by system performance.
 
 When in 'short' or 'long' mode, it will report the hash time value each time it
-is re-calculated
+is re-calculated.
 In 'short' or 'long' mode, the scan abort time starts at 5 seconds and uses the
 default 2.6316ns scan hash time, for the first 5 nonces or one minute
-(whichever is longer)
+(whichever is longer).
 
 In 'default' or 'value' mode the 'constants' are calculated once at the start,
-based on the default value or the value specified
+based on the default value or the value specified.
 The optional additional =N specifies to set the default abort at N 1/10ths of a
 second, not the calculated value, which is 112 for 2.6316ns
 
 To determine the hash time value for a non Icarus Rev3 device or an Icarus Rev3
 with a different bitstream to the default one, use 'long' mode and give it at
 least a few hundred shares, or use 'short' mode and take note of the final hash
-time value (Hs) calculated
+time value (Hs) calculated.
 You can also use the RPC API 'stats' command to see the current hash time (Hs)
-at any time
+at any time.
 
 The Icarus code currently only works with an FPGA device that supports the same
 commands as Icarus Rev3 requires and also is less than ~840Mh/s and greater
-than 2Mh/s
+than 2Mh/s.
 If an FPGA device does hash faster than ~840Mh/s it should work correctly if
-you supply the correct hash time nanoseconds value
+you supply the correct hash time nanoseconds value.
 
 The timing code itself will affect the Icarus performance since it increases
-the delay after work is completed or aborted until it starts again
+the delay after work is completed or aborted until it starts again.
 The increase is, however, extremely small and the actual increase is reported
-with the RPC API 'stats' command (a very slow CPU will make it more noticeable)
-Using the 'short' mode will remove this delay after 'short' mode completes
-The delay doesn't affect the calculation of the correct hash time
+with the RPC API 'stats' command (a very slow CPU will make it more noticeable).
+Using the 'short' mode will remove this delay after 'short' mode completes.
+The delay doesn't affect the calculation of the correct hash time.
 
 
 X6500
@@ -258,6 +257,7 @@ least the "dummy" mining bitstreams installed on them.
 
 If your boards do not have a mining bitstream yet, you must first, install
 ZTEX's BTCMiner (requires Java JDK version 6 or later) and install one.
+
 === WINDOWS NOTE ===
 Upon first powering up and connecting the board via USB, windows will attempt
 and fail to find the appropriate drivers.  To load the initial firmware on the
@@ -266,6 +266,7 @@ board, you'll need the EZ-USB FX2 SDK from here:
 Extract the firmware kit and use the driver within libusb-win32/ztex.inf.
 Windows should now recognize the board and you're ready to program it.
 === END OF WINDOWS ===
+
 Grab the latest miner jar from http://www.ztex.de/btcminer/#download and program
 the appropriate dummy firmware for your board.  The command should look
 something like (for a single FPGA board):

README.GPU

@@ -50,7 +50,8 @@ SETUP FOR GPU SUPPORT:
 
 To setup GPU mining support:
 
-Install AMD APP sdk, ideal version (see FAQ!) - put it into a system location.
+Install the AMD APP sdk, ideal version (see FAQ!) - put it into a system
+location.
 Download the correct version for either 32 bit or 64 bit from here:
 	http://developer.amd.com/tools/heterogeneous-computing/amd-accelerated-parallel-processing-app-sdk/downloads/
 
@@ -170,8 +171,8 @@ while not reaching overheat temperatures. As a lower clock speed limit, the
 auto-gpu mode checks the GPU card's "normal" clock speed and will not go below
 this unless you have manually set a lower speed in the range. Also, unless a
 higher clock speed was specified at startup, it will not raise the clockspeed.
-If the temperature climbs, fanspeed is adjusted and optimised before GPU engin
-e clockspeed is adjusted. If fan speed control is not available or already
+If the temperature climbs, fanspeed is adjusted and optimised before GPU engine
+clockspeed is adjusted. If fan speed control is not available or already
 optimal, then GPU clock speed is only decreased if it goes over the target
 temperature by the hysteresis amount, which is set to 3 by default and can be
 changed with:
@@ -313,10 +314,10 @@ A: Yes, pass a list separated by commas such as -I d,4,9,9
 
 Q: The CPU usage is high.
 A: The ATI drivers after 11.6 have a bug that makes them consume 100% of one
-CPU core unnecessarily so downgrade to 11.6. Binding BFGMiner to one CPU core on
-windows can minimise it to 100% (instead of more than one core). Driver version
-11.11 on linux and 11.12 on windows appear to have fixed this issue. Note that
-later drivers may have an apparent return of high CPU usage. Try
+CPU core unnecessarily, so downgrade to 11.6. Binding BFGMiner to one CPU core
+on windows can minimise it to 100% (instead of more than one core). Driver
+version 11.11 on linux and 11.12 on windows appear to have fixed this issue.
+Note that later drivers may have an apparent return of high CPU usage. Try
 'export GPU_USE_SYNC_OBJECTS=1' on Linux before starting BFGMiner. You can also
 set this variable in windows via a batch file or on the command line before
 starting BFGMiner with 'setx GPU_USE_SYNC_OBJECTS 1'
@@ -340,7 +341,7 @@ The starting fan speed is set to 50% in auto-fan mode as a safety precaution.
 
 Q: I upgraded BFGMiner version and my hashrate suddenly dropped!
 A: No, you upgraded your SDK version unwittingly between upgrades of BFGMiner
-and that caused your hashrate to drop. See the next question.
+and that caused your hashrate to drop. Please see the next question.
 
 Q: I upgraded my ATI driver/SDK/BFGMiner and my hashrate suddenly dropped!
 A: The hashrate performance in BFGMiner is tied to the version of the ATI SDK
@@ -380,7 +381,8 @@ uninstalling files so you may have to use third party tools like driversweeper
 to remove old versions. The other common reason for this is windows antivirus
 software is disabling one of the DLLs from working. If BFGMiner starts with the
 -T option but never starts without it, this is a sure fire sign you have this
-problem and will have to disable your antivirus or make exceptions.
+problem and will have to disable your antivirus or set up some exceptions in it
+if possible.
 
 Q: Is it faster to mine on Windows or Linux?
 A: It makes no difference. It comes down to choice of operating system for their
@@ -410,8 +412,8 @@ A: If you can install both drivers successfully (easier on windows) then yes,
 using the --gpu-platform option.
 
 Q: Can I mine with Nvidia or Intel GPUs?
-A: Yes, but their hashrate is very poor and likely you'll be using much more
-energy than you'll be earning in coins.
+A: Yes, but the hashrate on these is very poor and it is likely you'll be using
+much more energy than you'll be earning in coins.
 
 Q: Can I mine on both Nvidia and AMD GPUs at the same time?
 A: No, you must run one instance of BFGMiner with the --gpu-platform option for
@@ -422,11 +424,11 @@ A: With Nvidia you can, but with AMD you cannot.
 
 Q: I'm trying to mine a scrypt cryptocurrency but BFGMiner shows MH values
 instead of kH and submits no shares?
-A: Add the --scrypt parameter.
+A: Add the --scrypt parameter to your BFGMiner startup command.
 
 Q: I can't get anywhere near enough hashrate for scrypt compared to other
 people?
-A: You may not have enough system RAM as this is also required.
+A: You may not have enough system RAM, as this is also required.
 
 Q: My scrypt hashrate is high but the pool reports only a tiny proportion of my
 hashrate?
@@ -464,20 +466,20 @@ further but BFGMiner does not have access to these means.
 Q: I have multiple GPUs and although many devices show up, it appears to be
 working only on one GPU splitting it up.
 A: Your driver setup is failing to properly use the accessory GPUs. Your driver
-may be configured wrong or you have a driver version that needs a dummy plug on
-all the GPUs that aren't connected to a monitor.
+may be misconfigured or you have a driver version that needs a dummy plug on all
+the GPUs that aren't connected to a monitor.
 
 Q: I have some random GPU performance related problem not addressed above.
 A: Seriously, it's the driver and/or SDK. Uninstall them and start again,
-noting there is no clean way to uninstall them so you have to use extra tools
-or do it manually.
+also noting there is no clean way to uninstall them so you will likely have to
+use extra tools or do it manually.
 
 Q: Do I need to recompile after updating my driver/SDK?
 A: No. The software is unchanged regardless of which driver/SDK/ADL version you
 are running.
 
 Q: I do not want BFGMiner to modify my engine/clock/fanspeed?
-A: BFGMiner only modifies values if you tell it to via some parameters.
+A: BFGMiner only modifies values if you tell it to via the parameters.
 Otherwise it will just monitor the values.
 
 Q: Should I use crossfire/SLI?

README.OpenWrt

@@ -1,5 +1,5 @@
 Open up /etc/opkg.conf (on your router) in your favourite editor. You will see
-a line that looks similar to this at the top:
+a line that looks similar to this at the top (depending on your device):
 	src/gz attitude_adjustment http://downloads.openwrt.org/attitude_adjustment/12.09/ar71xx/generic/packages
 Note the platform following the OpenWrt version. In this example, it is ar71xx.
 

README.scrypt

@@ -1,5 +1,5 @@
 If you wish to donate to the author of scrypt support, Con Kolivas, for his past
-work (he no longer maintains this), please send your donations to
+work (he no longer maintains this), please send your donations to:
 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ
 
 ---
@@ -62,7 +62,7 @@ below to determine how many shaders your GPU has, and note that there are some
 variants of these cards, and Nvidia shaders are much much lower and virtually
 pointless trying to mine on. If this is not set, BFGMiner will query the
 device for how much memory it supports and will try to set a value based on
-that.
+that instead.
 SUMMARY: This will get you started but fine tuning for optimal performance is
 required.
 
@@ -179,7 +179,7 @@ Delete any .bin files so you're starting from scratch and see what bins get
 generated.
 
 First try without any thread concurrency or even shaders, as BFGMiner will try to
-find an optimal value
+find an optimal value:
 bfgminer -I 13
 
 If that starts mining, see what bin was generated, it is likely the largest
@@ -187,7 +187,7 @@ meaningful TC you can set.
 Starting it on mine I get:
 scrypt130302Tahitiglg2tc22392w64l8.bin
 
-See tc22392 that's telling you what thread concurrency it was. It should start
+Note that tc22392 tells you what thread concurrency it was. It should start
 without TC parameters, but you never know. So if it doesn't, start with
 --thread-concurrency 8192 and add 2048 to it at a time till you find the highest
 value it will start successfully at.

miner.c

@@ -1831,7 +1831,7 @@ static struct opt_table opt_config_table[] = {
 #endif // defined(unix)
 	OPT_WITHOUT_ARG("--net-delay",
 			opt_set_bool, &opt_delaynet,
-			"Impose small delays in networking to not overload slow routers"),
+			"Impose small delays in networking to avoid overloading slow routers"),
 	OPT_WITHOUT_ARG("--no-adl",
 			opt_set_bool, &opt_noadl,
 #ifdef HAVE_ADL