fix(gen): update

Author: SamyOubouaziz

pages/instances/reference-content/identify-devices.mdx

@@ -80,8 +80,8 @@ KERNEL=="sd*", ENV{ID_VENDOR}=="SCW", SYMLINK+="disk/scw/$env{ID_SERIAL_SHORT}"
 ```
 
 This rule will create a symlink `/dev/disk/scw/volume-<uuid>` (where `uuid` is the ID of the volume) for each volume:
+
 ```bash
-```sh
 root@test-instance:~# ls -l /dev/disk/scw/
 total 0
 lrwxrwxrwx 1 root root  9 Mar  7 16:18 volume-a5fb1cc7-70d3-457f-b4e0-a757997a4b33 -> ../../sda
@@ -97,27 +97,27 @@ VPC Private Networks to which the Instance is connected will appear as virtio PC
 
 As all PCI devices, they can be listed with the `lspci` command:
 
-```sh
+```bash
 
 root@test-instance:~# lspci -d '::0200'
 00:02.0 Ethernet controller: Red Hat, Inc. Virtio network device
 00:05.0 Ethernet controller: Red Hat, Inc. Virtio network device
-```bash
+00:06.0 Ethernet controller: Red Hat, Inc. Virtio network device
 ```
 
 The filter selects the Network controller device class/Ethernet controller device subclass. Three PCI devices are visible, which correspond to the public network device, and two VPC Private Network devices.
 By itself, the output of this command is not enough to distinguish between public and private networks, and can not distinguish between multiple private networks either: this simply confirms their existence in the PCI hierarchy of the Instance.
 
 More interestingly, network interfaces can be listed generically using the `ip link show` command:
 
-```sh
+```bash
 root@test-instance:~# ip link show
 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 2: ens2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
     link/ether de:00:00:e1:7e:f2 brd ff:ff:ff:ff:ff:ff
     altname enp0s2
-```bash
+3: ens5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
     link/ether 02:00:00:b7:c8:a5 brd ff:ff:ff:ff:ff:ff
     altname enp0s5
 4: ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
@@ -130,8 +130,8 @@ Here, four interfaces are listed, one of which (`lo`) is the virtual loopback in
 A simple and effective way to distinguish the public network interface from the VPC Private Network interfaces is the MAC address prefix. VPC Private Network interfaces always have a MAC address starting with `02:00:00`.
 
 Using the JSON output mode of the `ip` command  and filtering with the `jq` JSON parser, we can thus list VPC Private Network interfaces:
+
 ```bash
-```sh
 root@test-instance:~# ip -j link | jq -r '.[] | select(.address | test("02:00:00:.*")) | .ifname'
 ens5
 ens6
@@ -140,7 +140,7 @@ ens6
 Using the MAC address of the interfaces, it is also possible to distinguish between the different VPC Private Network interfaces. The MAC address of each interface is available through the API.
 For example, querying `/instances/v1/<zone>/servers/<uuid>/private_nics`, where `<zone>` is the zone of the server and `<uuid>` is the ID of the Instance gives:
 
-```sh
+```bash
 {
   "private_nics": [
     {
@@ -151,7 +151,7 @@ For example, querying `/instances/v1/<zone>/servers/<uuid>/private_nics`, where
       "state": "available",
       "creation_date": "2024-03-13T14:42:55.822512+00:00",
       "modification_date": "2024-03-13T14:42:57.401901+00:00",
-```bash
+      "zone": "fr-par-1",
       "tags": []
     },
     {
@@ -160,7 +160,7 @@ For example, querying `/instances/v1/<zone>/servers/<uuid>/private_nics`, where
       "server_id": "02f28852-b7b3-4cfc-9682-c7d14a044f29",
       "mac_address": "02:00:00:c1:72:51",
       "state": "available",
-```bash
+      "creation_date": "2024-03-13T15:24:07.686223+00:00",
       "modification_date": "2024-03-13T15:24:08.647484+00:00",
       "zone": "fr-par-1",
       "tags": []