Fix: broken output in Documentation Code Snippets

backends/dpdk/README.md

@@ -68,7 +68,7 @@ To load the 'spec' file in dpdk follow the instructions in the
 - Currently, programs written for DPDK target should limit the functionality in Ingress blocks, in case non empty  Egress blocks are present it will be ignored by default unless Hidden temporary option `--enableEgress` used.  When egress block support gets added to the DPDK target, and compiler can generate separate spec file for non empty ingress and egress blocks then option `--enableEgress` will be removed.
 - DPDK architecture assumes the following signatures for programmable block of PSA. P4C-DPDK converts the input program to this form.
 
-```P4
+``` P4
 parser IngressParser (packet_in buffer, out H parsed_hdr, inout M user_meta);
 
 control Ingress (inout H hdr, inout M user_meta);

backends/ebpf/README.md

@@ -280,7 +280,7 @@ state transition | `goto` statement
 `extract` | load/shift/mask data from packet buffer
 
 #### Translating match-action pipelines
-##
+
 P4 Construct | C Translation
 ----------|------------
 table     | 2 eBPF tables: second one used just for the default action
@@ -385,7 +385,7 @@ The C extern could be also allowed to access packet’s payload, but this featur
 
 The custom C extern function should be explicitly declared in the P4 program making use of that extern. For example:
 
-```C
+```c
 /** Declaration of the C extern function. */
 extern bool verify_ipv4_checksum(in IPv4_h iphdr);
 ```
@@ -425,7 +425,7 @@ clang -O2 -include C-EXTERN-FILE.c -target bpf -c OUTPUT.c -o OUTPUT.o
 
   * BPF maps can be defined inside the C extern function to provide statefulness. BPF map can be defined as follows:
 
-  ```C
+  ```c
   REGISTER_START()
   REGISTER_TABLE(<NAME>, BPF_MAP_TYPE_HASH, <KEY-SIZE>, <VALUE-SIZE>>, <MAX_ENTRIES>)
   REGISTER_END()