Trimmed trailing whitespace and blank lines

Author: wtschueller

ATtiny85_doc/README.md

@@ -4,22 +4,22 @@
 <img src="https://goo.gl/7cxEmm" width="500">
 </p>
 
-Follow those steps for use the Arduino as ISP:  
-- Load the sketch "ArduinoISP" on your Arduino  
-- Connect the Arduino with "ArduinoISP" to the ATtiny85. Use the schematic in this folder.  
-- Open your ATtiny85 program and select:  
-  * "tools" --> "board" --> "ATtiny"  
-  * "tools" --> "processor" --> "ATtiny85"  
+Follow those steps for use the Arduino as ISP:
+- Load the sketch "ArduinoISP" on your Arduino
+- Connect the Arduino with "ArduinoISP" to the ATtiny85. Use the schematic in this folder.
+- Open your ATtiny85 program and select:
+  * "tools" --> "board" --> "ATtiny"
+  * "tools" --> "processor" --> "ATtiny85"
   * "tools" --> "programmer" --> "Arduino as ISP(ATtinycore)"
 
-**IF** it's the **first time** you use the ATtiny OR you want to **change the frequency** (Mhz) OR **BOD settings**, you must burn the bootloader:  
-  - "tools" --> Burn Bootloader  
+**IF** it's the **first time** you use the ATtiny OR you want to **change the frequency** (Mhz) OR **BOD settings**, you must burn the bootloader:
+  - "tools" --> Burn Bootloader
 
 Now you can upload your sketch.
 
 
 ### The 0,1 uF capacitor
-All ATTiny chips (as well as the vast majority of digital integrated circuits) require a 0.1uF ceramic capacitor between Vcc and Gnd for decoupling; this should be located as close to the chip as possible (minimize length of wires to cap). Devices with multiple Vcc pins, or an AVcc pin, should use a cap on those pins too. Do not be fooled by poorly written tutorials or guides that omit these.  
+All ATTiny chips (as well as the vast majority of digital integrated circuits) require a 0.1uF ceramic capacitor between Vcc and Gnd for decoupling; this should be located as close to the chip as possible (minimize length of wires to cap). Devices with multiple Vcc pins, or an AVcc pin, should use a cap on those pins too. Do not be fooled by poorly written tutorials or guides that omit these.
 
 ### The 10 uF capacitor
 The capacitor prevents the Arduino board from resetting (which starts the bootloader), thus ensuring that the Arduino IDE talks to the ArduinoISP (not the bootloader) during the upload of sketches.

README.md

@@ -1,20 +1,20 @@
 # ATTinyCore **Universal**
 Arduino support for almost every classic tinyAVR device! Supports ATtiny 1634, 2313/4313, 24/44/84, 441/841, 25/45/85, 261/461/861, 87/167, 48/88, 43 and 828. Supports programming vis ISP, Serial (Optiboot - all parts with >4k flash, and all parts with 4k flash for which an 8k version is available) or VUSB (Micronucleus - where appropriate)
 ## State of ATTinyCore
-Development of ATTinyCore is proceeding in the v2.0.0-dev branch. 
+Development of ATTinyCore is proceeding in the v2.0.0-dev branch.
 
 **PLEASE DO NOT SUBMIT PR's AGAINST the "MASTER" BRANCH
 YOUR CHANGES WILL BE LOST UPON THE NEXT RELEASE IF YOU DO
 NEW CHANGES NEED TO GO INTO v2.0.0-dev**  (which will be my next project after DxCore 1.3.7 release this week)
 
 ## We desperately need testing help here
 **THE 2.0.0-dev branch IS NOW READY FOR PUBLIC TESTING VIA MANUAL INSTALLATION**
-It i **CRITICAL** that we get as much testing done as possible because **BASICALLY NOTHING HAS BEEN TESTED**, and virtually no files are without major fundamnental changes! 
+It i **CRITICAL** that we get as much testing done as possible because **BASICALLY NOTHING HAS BEEN TESTED**, and virtually no files are without major fundamnental changes!
 
 *There are 272 different versions of micronucleus built (and part of the 2.0.0-dev branch now), and optiboot will dwarf that number!*
-0 of those have been teted. Obviously we are leaning *very* heavily on automation of configuration generation for this release. 
+0 of those have been teted. Obviously we are leaning *very* heavily on automation of configuration generation for this release.
 
-Half of the tinyNeoPixel speeds have had the assembly routines modified in major ways (there's no more stupid menu for the port), but they are untested. I have a TON of irons in the fire right now, and I am trying to get this out and stop delaying it and delaying it. 
+Half of the tinyNeoPixel speeds have had the assembly routines modified in major ways (there's no more stupid menu for the port), but they are untested. I have a TON of irons in the fire right now, and I am trying to get this out and stop delaying it and delaying it.
 
 If you find problems with 2.0.0-dev (you can just create a "hardware" folder in your sketchbook and sync the repo to that location to nanually install - no need to do anything wacky like on my other cores), create an issue, start a discussion, or hell even just email me with info, just get the information to me somehow.
 
@@ -23,7 +23,7 @@ Thank you users!
 ## [Check it out, we have "discussions" now!](https://github.com/SpenceKonde/ATTinyCore/discussions)
 Let's use that, not gitter.
 
-### Current **strongly** recommended IDE version: 1.8.13 or later. 
+### Current **strongly** recommended IDE version: 1.8.13 or later.
 Users of 1.6.x versions should use caution with any board manager packages as the handling of dependency versions, at least under 1.6.9, appears to be severely broken, such that installing one packages can break others. For example, DxCore won't work if ATYTinyCore is installed on 1.6.9! - both cores correctly specify their requirements, but the IDE does not use the correct versions of the toochain. It is likely that similar bugs involving other tools also manifest here. Use 1.8.13 or similar recent version if at all possible; if you are unwilling or unable to update your main Arduino IDE version, a "portable" installation is recommended - the separate copy of IDE *with portable installation* should ensure that what you do in that version does not effect the other version - if you can't use 1.8.13, a portable 1.6.9 version will achieve the same thing, only without the other fixes and improvements that went into the IDE since then.
 
 

avr/extras/README.md

@@ -307,4 +307,3 @@ The Tools -> millis()/micros() allows you to enable or disable the millis() and
 ## Memory Lock Bits, disabling Reset
 
 ATTinyCore will never set lock bits automatically, nor will it set fuses to disable ISP programming (it is intentionally not made available as an option, since after doing that, an HVSP programmer is needed to further reprogram the chip, and inexperienced users would be at risk of bricking their chips this way). The usual workflow when these bits are in use is Set other fuses -> Upload -> Test -> set the lockbits and/or fuses. This can be done from the command line using AVRdude. To expedite the process, you can enable "Verbose Upload" in preferences, do "burn bootloader" (the board and/or programmer does not need to be present), scroll to the top of the output window - the first line is the avrdude command used to burn the bootloader, including the paths to all the relevant files. It can be used as a template for the command you execute to set the fuse/lock bits. Disabling of reset is currently not an option, either - but for bootloader boards, this may change - VUSB bootloaders which disable reset are in widespread use, seemingly without issue. It will never be an option for non-bootloader boards because of the convoluted workflow required.
-

avr/extras/UsingMicronucleus.md

@@ -60,7 +60,7 @@ uint8_t resetcause = GPIOR0;
 if(resetcause == 0) {
   resetcause = MCUSR;
   MCUSR = 0;
-} 
+}
 // if you use GPIOR0 in your code
 else {
   GPIOR0 = 0;