docs: second pass on casiplot module

docs/sh/modcasioplot-en.md

@@ -25,7 +25,7 @@ draw_string(x: int, y: int, text: str, ?color: (int, int, int), ?size: str) -> N
 
 The rendering area is of size 128x64 on G-III and 384x216 on fx-CG. While the G-III supports only two colors (black and white), the fx-CG supports 65536 colors (16-bit RGB565). Still, the color format is _always_ (r,g,b) triplets with 0 ≤ r,g,b ≤ 255. This helps compatibility between models and with PC, at a performance cost. Calculators process these colors by _approximating_ them to the closest color they can represent.
 
-Like the gint module, `casioplot` functions draw to an internal buffer called the VRAM, and only pushes that to the screen when explicitly asked to or at the end of the program.
+Like the gint module, `casioplot` functions draw to an internal buffer called the VRAM, and the module only pushes that to the screen when explicitly asked to or at the end of the program.
 
 `show_screen()` pushes the VRAM to screen after something has been drawn.
 
@@ -43,7 +43,7 @@ TODO: Example
 
 _Text mode._ `casioplot` automatically switches PythonExtra into graphics mode when imported. Programs that want to render graphics frames after a `print()` should `show_screen()` _before_ rendering the first frame since `print()` switches to text mode.
 
-_Performance._ Writing to VRAM is the main reason why rendering in `casioplot` is sometimes much faster than in Basic. Basic pushes the rendered data to the display after every call, which is slow. Unfortunately, `casioplot` ends up losing for complex drawing tasks for which Basic has complex functions (like DrawStat) while `casioplot` just as single pixels. In this case, functions from the [gint module](modgint-en.md) can be of help.
+_Performance._ Writing to VRAM is the main reason why rendering in `casioplot` is sometimes much faster than in Basic. Basic pushes the rendered data to the display after every call, which is slow. Unfortunately, `casioplot` ends up losing for complex drawing tasks for which Basic has complex functions (like DrawStat) while `casioplot` just has single pixels. In this case, functions from the [gint module](modgint-en.md) can be of help.
 
 ## Differences with the official `casioplot` module
 

docs/sh/modcasioplot-fr.md

@@ -10,8 +10,8 @@ from casioplot import *
 
 **Sommaire**
 - [Fonctions de dessin](#fonctions-de-dessin)
-- [Considérations spéciale pour le rendu](#considerations-speciales-pour-le-rendu)
-- [Différences avec le module `casioplot` officiel](#differences-avec-le-module-casioplot-officiel)
+- [Considérations spéciales pour le rendu](#considérations-spéciales-pour-le-rendu)
+- [Différences avec le module `casioplot` officiel](#différences-avec-le-module-casioplot-officiel)
 
 ## Fonctions de dessin
 
@@ -39,7 +39,7 @@ Comme le module gint, `casioplot` dessine systématiquement dans un buffer inter
 
 TODO: Exemple
 
-## Considérations spéciale pour le rendu
+## Considérations spéciales pour le rendu
 
 _Mode texte._ `casioplot` passe automatiquement PythonExtra en mode graphique à l'import. Les programmes qui veulent faire du dessin graphique après un `print()` doivent appeler `show_screen()` _avant_ de commencer à dessiner le premier frame parce que `print()` repasse en mode texte.