MD lint

Author: SpenceKonde

README.md

@@ -669,7 +669,7 @@ As promised, a bunch of additional information was released; Unfortunately it le
 ## Warnings and Caveats
 There are however a few cautions warranted regarding megaTinyCore - either areas where the core is different from official cores, or where the behavior is the same, but not as well known.
 
-### Linker sometimes fails on 8k parts due to an apparent compiler bug.
+### Linker sometimes fails on 8k parts due to an apparent compiler bug
 It doesn't seem to know it can wrap around with rjmp, and if would have to, it fails to link. This is only relevant on 8k parts. All I can advise is to not use those parts. Considering that 16k parts arent't much more expensive..
 
 
@@ -681,8 +681,8 @@ Therefore:
   * `takeOverTCxn()` has been called (`resumeTCxn()` to reverse this and reinitialize the timer to restore the functionality is available on DxCore, but I question the value of it and have not ported it).
     * If present, since resume reverses takeOver and reinitializes the timer for analogWrite PWM, you must not call it between when you called takeOver and when you write to register
   * You are changing only registers described in the relevant core documentation for that timer as being safe to modify without calling `takeOverTCxn()`.
-    * The more complicated the timer, logically, the more likely it is that someone will be able to comprehend register manipulation relevant to their application without understanding the rest of the chapter (of datasheet) well enough to take full control as with a takeOver. In recognition of that (as well as the empirical observation that strange reconfiguration of the TCA is extremely common, as were questions about that prior to the introducution of relevant examples), we concluded that unlike the TCA, which is a well-behaved, very mundanetimer that is familiar, conceptually, to anyone who's useda classic AVR's TIMER1, the TCD is neither cooperative nor familiar, and few users are likely to be able to reconfigure it fully themselves, so while takeOverTCD0() is offered on partswith a TCD, we also put further effort into ensuring that as many options as possiblethat might plausibly be used with PWM could be altered while still using `analogWrite()`. These were documented in [the TCD reference](/megaavr/extras/Ref_TCD.md).
-    * The much shorter list for TCA remains in the [timer reference](/egaavr/extras/Ref_Timers.md), as TCA has few relevant options not already controlled by analogWrite which are relevant when takeOverTCA0() is not called.
+    * The more complicated the timer, logically, the more likely it is that someone will be able to comprehend register manipulation relevant to their application without understanding the rest of the chapter (of datasheet) well enough to take full control as with a takeOver. In recognition of that (as well as the empirical observation that strange reconfiguration of the TCA is extremely common, as were questions about that prior to the introducution of relevant examples), we concluded that unlike the TCA, which is a well-behaved, very mundanetimer that is familiar, conceptually, to anyone who's useda classic AVR's TIMER1, the TCD is neither cooperative nor familiar, and few users are likely to be able to reconfigure it fully themselves, so while takeOverTCD0() is offered on partswith a TCD, we also put further effort into ensuring that as many options as possiblethat might plausibly be used with PWM could be altered while still using `analogWrite()`. These were documented in [the TCD reference](megaavr/extras/Ref_TCD.md).
+    * The much shorter list for TCA remains in the [timer reference](megaavr/extras/Ref_Timers.md), as TCA has few relevant options not already controlled by analogWrite which are relevant when takeOverTCA0() is not called.
   * You do not use any builtin functions that directly or indirectly call `analogWrite()`, `turnOffPWM()` or `digitalWrite()`
 * Reconfiguring the millis timer will break timekeeping very badly. If you need to reconfigure all the timers, such that you can't use the tools menu to put millis on a timer you don't need to reconfigure (ex, you need to use Servo and `tone()`, and reconfigure TCA for custom PWM on a tinyAVR 2), disable millis from the menu, whi
 

megaavr/cores/megatinycore/wiring_analog.c

@@ -1115,7 +1115,6 @@ void analogWrite(uint8_t pin, int val) {
     return;
   }
   #if defined(TCD0) && defined(USE_TIMERD0_PWM) && defined(NO_GLITCH_TIMERD0)
-
     uint8_t set_inven = 0;
   #endif
   // Set pin output because that's what Arduino does
@@ -1286,7 +1285,7 @@ void analogWrite(uint8_t pin, int val) {
   /**********************************************************************
   * PART 3.5: TIMERD noglitch
   **********************************************************************/
-          #if defined(NO_GLITCH_TIMERD0) // This mode is always used with the stock variant.
+          #if defined(NO_GLITCH_TIMERD0) // This mode is no longer used by default, as it caused some other problems.
             #if defined(USE_TCD_WOAB) && _AVR_PINCOUNT != 8
               // TCD is on PA4 or PA5 on 14+ pin parts
               if (set_inven == 0) { // we are not setting invert to make the pin HIGH when not set; either was 0 (just set CMPxSET > CMPBCLR) or somewhere in between.