Deployed 0cd98c6 with MkDocs version: 1.6.1

FAQs/index.html

@@ -823,7 +823,7 @@
 <ul>
 <li>ESP32CAM hardware antenna design is very poor in connection with camera frequency.</li>
 <li>Simple test: When the device is in operation, putting your thumb on the camera connector and the directly adjacent components should make the device respond more quickly.</li>
-<li>Possible optimization: Here, an attempt was made to dampen the frequency influences somewhat by shielding. 
+<li>Possible optimization: Here, an attempt was made to dampen the frequency influences somewhat by shielding.
 <a href="https://www.reddit.com/r/esp32/comments/r9g5jc/fixing_ymmv_the_poor_frame_rate_on_the_esp32cam/">Shielding Example</a></li>
 <li>WLAN channel: Preferably use channel 1, 6 or 11</li>
 <li>Performance can vary depending on the AP manufacturer. If necessary, check with a mobile hotspot or other device to exclude AP influence</li>
@@ -843,7 +843,7 @@
 <li>Are you trying to read digits, an analog dial, or both?</li>
 <li>etc.</li>
 </ul>
-<p>Anecdotally, the authors of this page have great success with the meter. While the AI algorithm itself is not perfect and sometimes returns <code>NaN</code> or incorrect values, other post-processing / prevalue / sanity checks help ensure such invalid values are filtered out. With the correct settings, one author has been running this device for 1 month without any incorrect values reported. </p>
+<p>Anecdotally, the authors of this page have great success with the meter. While the AI algorithm itself is not perfect and sometimes returns <code>NaN</code> or incorrect values, other post-processing / prevalue / sanity checks help ensure such invalid values are filtered out. With the correct settings, one author has been running this device for 1 month without any incorrect values reported.</p>
 <p>See the FAQs below for more details and configuration hints.</p>
 <h2 id="my-numbers-are-not-correctly-detected-what-can-i-do"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.4</span> My numbers are not correctly detected. What can I do?</h2>
 <ul>
@@ -867,32 +867,32 @@
 <p>The neutral position (no rolling) is not perfectly at zero, but rather at something like 7.9 or 8.1, even if it should be exactly 8</p>
 </li>
 <li>
-<p>The "PostProcessingAlgo" is trying to judge out of the individual readings, what number it should be. </p>
+<p>The "PostProcessingAlgo" is trying to judge out of the individual readings, what number it should be.</p>
 </li>
 <li>
 <p>For example if the previous number is a "1", but the next number seems to be a "8.9", most probably there was a "zero crossing" and the number is a "9" and not still an "8"</p>
 </li>
 <li>
-<p>Currently the setting of the algorithm is set to fit most of the meters and cases. But the parameters do not fit perfectly for all situations. Therefore there might be intermediate states, where the reading is false. 
+<p>Currently the setting of the algorithm is set to fit most of the meters and cases. But the parameters do not fit perfectly for all situations. Therefore there might be intermediate states, where the reading is false.
   This is especially the case, at the positions, where the roll over (zero crossing) is just starting.</p>
 </li>
 <li>To prevent a sending of false parameters, there is the possibility to limit the maximum allowed change (MaxRateChange).
   Usually after some time and movement of the counters a bit further, the reading is getting back to a stable reading.</li>
-<li>To handle this, a parametrized setting would be needed. This is rather complicated to implement as subtle changes make a relevant difference. Currently this is not implemented. 
+<li>To handle this, a parametrized setting would be needed. This is rather complicated to implement as subtle changes make a relevant difference. Currently this is not implemented.
   So please be a bit patient with your meter :-)</li>
 </ul>
 <h2 id="pre-value"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.7</span> Pre-Value</h2>
 <p>PreValue is here a bit missleading, because normally it is the same as the last value. In the next round of reading it will be used to check negative rates, high rates (MaxRateValue / MaxRateType) and CheckDigitIncreaseConsistency (dig-class11 only). Either from a previous correctly identified value or manual setting by the user.</p>
-<p>If you use post processes, enable the pre-value. The pre-value must be set at first time. Set it to the current raw value. </p>
+<p>If you use post processes, enable the pre-value. The pre-value must be set at first time. Set it to the current raw value.</p>
 <p>If the device runs in errors, the pre-value will not be updated, as long as the <code>preValueAgeStartup</code> time between the last valid value (or startup time) and current time is not exceeded. After it the preValue will be set again, if no other error occured. So the device can not run in an endless error, like high rate.</p>
 <h2 id="rate-too-high-read"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.8</span> "Rate too high - Read: ..."</h2>
 <p>In configuration you can set the <code>MaxRateValue</code> and <code>MaxRateType</code>. The settings suppress improbably high values that can come from false readings. To do this, the value must be set correctly depending on your meter.</p>
 <p>Before doing this, you should be clear about the type of rating you want to use.</p>
 <ul>
-<li><code>Absolute change</code> is the interval between two readings - no matter how often the readings happen. </li>
-<li><code>RateChange</code> is the change per minute. This is calculated from the time difference between the last and the current reading. </li>
+<li><code>Absolute change</code> is the interval between two readings - no matter how often the readings happen.</li>
+<li><code>RateChange</code> is the change per minute. This is calculated from the time difference between the last and the current reading.</li>
 </ul>
-<p>If there is an interval of 5 minutes between readings and a MaxRateValue of 1, an error "Rate too high - Read: ..." if </p>
+<p>If there is an interval of 5 minutes between readings and a MaxRateValue of 1, an error "Rate too high - Read: ..." if</p>
 <ul>
 <li>Absolute change: the difference is <code>&gt; 1</code></li>
 <li>RateChange: the difference is <code>&gt; 1 / 5</code></li>