spellcheck

Author: SpenceKonde

megaavr/libraries/Comparator/README.md

@@ -86,7 +86,7 @@ comparator::in_n::vref;   // Use the voltage reference w/out DAC (0/1-series onl
 comparator::in_n::dacref; // Use DACREF as input,
 ```
 #### What is the DACREF?
-On the tinyAVR 1-series, a new feature was added to the ACs: The parts had an 8-bit DAC, so they tied it to the AC's negative mux, an obvious choice. When they added the extra AC's on the 16k and 32k parts, they wanted to have the sme functionality on the other AC's (as it was very well suited to things like windowed mode, which was now posible), so they added two more DAC instances which didn't have an output buffer, and were used only for the AC's. That seemed to be a great combination, and was adopted from the mega0-series onwards built into the AC and called the DACREF. At this point, it replaced the previous VREF option entirely, and when the DAC returned as a peripheral in the Dx-series, it was independent of the ACs. In fact, it isn't even routed to the AC's; the DAC there gets direct internal connections to the ADC and the OPAMPS but nt the ACs.
+On the tinyAVR 1-series, a new feature was added to the ACs: The parts had an 8-bit DAC, so they tied it to the AC's negative mux, an obvious choice. When they added the extra AC's on the 16k and 32k parts, they wanted to have the same functionality on the other AC's (as it was very well suited to things like windowed mode, which was now possible), so they added two more DAC instances which didn't have an output buffer, and were used only for the AC's. That seemed to be a great combination, and was adopted from the mega0-series onwards built into the AC and called the DACREF. At this point, it replaced the previous VREF option entirely, and when the DAC returned as a peripheral in the Dx-series, it was independent of the ACs. In fact, it isn't even routed to the AC's; the DAC there gets direct internal connections to the ADC and the OPAMPS but nt the ACs.
 
 #### Usage
 ``` c++

megaavr/libraries/Wire/README.md

@@ -60,7 +60,7 @@ The size of the buffer is based simply on the available RAM on the part (note th
 --------|-------------|---------------------|---------------------
  <256b  | 16b         | 2k tinyAVR parts    | The 128b ram parts do not have space for 32-byte buffers. Note that many libraries may unknowingly rely on a 32+ bit buffer.
  <4096  | 32b         | Almost everything   | 32b buffers are the default.
- >4095  | 130b        | 32k+ Dx, some Ex    | 130b allows a full 128b page write (including the two address bytes) to be sent to a 24-series I2C EEPROM;<br/> that's the largest blob of data I am aware of people hving reason to send over I2C <br/>(and these parts can afford the memory, unlike the tinyAVR). <br/>(Note that EEPROM sizes on modern AVRs are smaller than classic ones, and some also have signifiantly lower flash endurance, <br/> so there may be more reason to use such things now).
+ >4095  | 130b        | 32k+ Dx, some Ex    | 130b allows a full 128b page write (including the two address bytes) to be sent to a 24-series I2C EEPROM;<br/> that's the largest blob of data I am aware of people hving reason to send over I2C <br/>(and these parts can afford the memory, unlike the tinyAVR). <br/>(Note that EEPROM sizes on modern AVRs are smaller than classic ones, and some also have significantly lower flash endurance, <br/> so there may be more reason to use such things now).
 
 ## Official specification of I2C
 [From NXP, the current owner of the relevant IP](https://www.nxp.com/docs/en/user-guide/UM10204.pdf)