chore(docs) remove unneeded eval_rst statements

docs/porting/display.md

@@ -1,5 +1,3 @@
-```eval_rst
-```
 # Display interface
 
 To register a display for LVGL, a `lv_disp_draw_buf_t` and a `lv_disp_drv_t` variable have to be initialized.

docs/porting/gpu.md

@@ -1,5 +1,3 @@
-```eval_rst
-```
 # Add custom GPU
 LVGL has a flexible and extendable draw pipeline. You can hook it to do some rendering with a GPU or even completely replace the built-in software renderer.
 

docs/porting/indev.md

@@ -1,5 +1,3 @@
-```eval_rst
-```
 # Input device interface
 
 ## Types of input devices

docs/porting/index.md

@@ -1,5 +1,3 @@
-```eval_rst
-```
 
 # Porting
 

docs/porting/log.md

@@ -1,5 +1,3 @@
-```eval_rst
-```
 # Logging
 
 LVGL has a built-in *Log* module to inform the user about what is happening in the library.

docs/porting/os.md

@@ -1,5 +1,3 @@
-```eval_rst
-```
 # Operating system and interrupts
 
 LVGL is **not thread-safe** by default.

docs/porting/project.md

@@ -1,5 +1,3 @@
-```eval_rst
-```
 
 # Set up a project
 

docs/porting/sleep.md

@@ -1,5 +1,3 @@
-```eval_rst
-```
 # Sleep management
 
 The MCU can go to sleep when no user input happens. In this case, the main `while(1)` should look like this:

docs/porting/tick.md

@@ -1,5 +1,3 @@
-```eval_rst
-```
 # Tick interface
 
 LVGL needs a system tick to know elapsed time for animations and other tasks.

docs/porting/timer-handler.md

@@ -1,5 +1,3 @@
-```eval_rst
-```
 # Timer Handler
 
 To handle the tasks of LVGL you need to call `lv_timer_handler()` periodically in one of the following: