From bbb07952ca0311e09160e15fb607937828c3b98b Mon Sep 17 00:00:00 2001 From: Otto Winter Date: Wed, 12 Dec 2018 16:24:43 +0100 Subject: [PATCH] Fix --- esphomeyaml/components/output/esp8266_pwm.rst | 8 +++----- seo.py | 2 +- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/esphomeyaml/components/output/esp8266_pwm.rst b/esphomeyaml/components/output/esp8266_pwm.rst index 0a123a988..c15e30cd8 100644 --- a/esphomeyaml/components/output/esp8266_pwm.rst +++ b/esphomeyaml/components/output/esp8266_pwm.rst @@ -7,11 +7,9 @@ ESP8266 Software PWM Output The ESP8266 Software PWM platform allows you to use a software PWM on the pins GPIO0-GPIO16 on your ESP8266. As this is only a software PWM -and not a hardware PWM (like the :doc:`ESP32 LEDC PWM `) and has a few -limitations. - -- There can be a noticeable amount of flickering with increased WiFi activity. -- The output range only goes up to about 80%. +and not a hardware PWM (like the :doc:`ESP32 LEDC PWM `) and has a key +disadvantage: There can be a noticeable amount of flickering with increased WiFi +activity. If you need a stable PWM signal, it’s definitely recommended to use the successor of the ESP8266, the ESP32, and its :doc:`ESP32 LEDC PWM ` instead. diff --git a/seo.py b/seo.py index d8fd3b112..bb83a0605 100644 --- a/seo.py +++ b/seo.py @@ -52,7 +52,7 @@ def seo_visit(self: HTMLTranslator, node: SEONode): # Twitter create_content_meta("twitter:title", node.title) create_content_meta("twitter:image:src", node.image) - create_content_meta("twitter:card", "summary_large_image") + create_content_meta("twitter:card", "summary") create_content_meta("twitter:site", "@OttoWinter_") create_content_meta("twitter:creator", node.author_twitter) create_content_meta("twitter:description", node.description)