README.org: Add CUSTOM_id props to correct rendering via go-org

See: https://github.com/niklasfasching/go-org/issues/32#issuecomment-1546940722

README.org

@@ -64,6 +64,9 @@ From this we extract the necessary guix bootloader configuration options (for se
 - terminal-outputs :: console serial
 
 *** Manual modifications to Debian's Grub
+:PROPERTIES:
+:CUSTOM_ID: manual_modifications_to_debians_grub
+:END:
 
 Modify grub config on debian to add an additional (and default) option to chainload Guix
 grub.
@@ -108,6 +111,9 @@ Using the a snippet taken from ~/etc/network/interfaces~ on the existing debian
 #+end_src
 
 ** Disk Partitioning
+:PROPERTIES:
+:CUSTOM_ID: disk_partitioning
+:END:
 
 For this installation we are using ~/dev/sda~ (a 1.5T ssd which is faster then the
 alternative 3.6T ssd in the server).
@@ -281,9 +287,9 @@ bootstrap a system like this often.
 
 With the Debian VM setup, we can now apply the documented bootstrapping steps.
 
-1. [[*Disk Partitioning][Disk Partitioning]], but with disks adjusted to match the testing VM.
-2. [[*Bootstrap Guix][Bootstrap Guix]], ensure ~<EFI-UUID>~ matches the VM efi partition used for Guix.
-3. [[*Manual modifications to Debian's Grub][Manual modifications to Debian's Grub]], again ensuring ~<EFI-UUID>~ matches the VM efi
+1. [[#disk_partitioning][Disk Partitioning]], but with disks adjusted to match the testing VM.
+2. [[#bootstrap_guix][Bootstrap Guix]], ensure ~<EFI-UUID>~ matches the VM efi partition used for Guix.
+3. [[#manual_modifications_to_debians_grub][Manual modifications to Debian's Grub]], again ensuring ~<EFI-UUID>~ matches the VM efi
    partition used for Guix.
 4. Reboot
 
@@ -302,6 +308,9 @@ testable.
   networking service will not be able to start.
 
 * Bootstrap Guix
+:PROPERTIES:
+:CUSTOM_ID: bootstrap_guix
+:END:
 
 Using Guix on debian, bootstrap the machine using the configuration in [[*Define Guix operating-system for the machine][Define Guix
 operating-system for the machine]].