Update edf.md

Author: gwangmu

docs/software/container-engine/edf.md

@@ -7,9 +7,9 @@ EDF files use the [TOML format](https://toml.io/en/). For details about the data
 
 In the following, the default value is none (i.e., the empty value of the corresponding type) if not specified.
 
-### (ARRAY or STRING) base_environment
+### base_environment
 
-Ordered list of EDFs that this file inherits from. Parameters from listed environments are evaluated sequentially. Supports up to 10 levels of recursion.
+(ARRAY or STRING) Ordered list of EDFs that this file inherits from. Parameters from listed environments are evaluated sequentially. Supports up to 10 levels of recursion.
 
 !!! example
      * Single environment inheritance:
@@ -27,9 +27,9 @@ Ordered list of EDFs that this file inherits from. Parameters from listed enviro
      * The individual EDF entries in the array follow the same search rules as the arguments of the `--environment` CLI option for Slurm; they can be either file paths or filenames without extension if the file is located in the [EDF search path][ref-ce-edf-search-path].
      * This parameter can be a string if there is only one base environment.
 
-### (STRING) image
+### image
 
-The container image to use. Can reference a remote Docker/OCI registry or a local Squashfs file as a filesystem path.
+(STRING) The container image to use. Can reference a remote Docker/OCI registry or a local Squashfs file as a filesystem path.
 
 !!! example
      * Reference of Ubuntu image in the Docker Hub registry (default registry)
@@ -64,9 +64,9 @@ The container image to use. Can reference a remote Docker/OCI registry or a loca
          * `[:TAG]`: (optional) image tag name, preceded by :.
      * The registry user can also be specified in the `$HOME/.config/enroot/.credentials` file.
 
-### (STRING) workdir
+### workdir
 
-Initial working directory when the container starts. Default: inherited from image.
+(STRING) Initial working directory when the container starts. Default: inherited from image.
 
 !!! example
      * Workdir pointing to a user defined project path 
@@ -78,27 +78,27 @@ Initial working directory when the container starts. Default: inherited from ima
         workdir = "/tmp"
         ```
 
-### (BOOL) entrypoint
+### entrypoint
 
-If true, run the entrypoint from the container image. Default: true.
+(BOOL) If true, run the entrypoint from the container image. Default: true.
 
 !!! example
     ```bash
     entrypoint = false
     ```
 
-### (BOOL) writable
+### writable
 
-If false, the container filesystem is read-only. Default: true.
+(BOOL) If false, the container filesystem is read-only. Default: true.
 
 !!! example
     ```bash
     writable = true
     ```
 
-### (ARRAY) mounts
+### mounts
 
-List of bind mounts in the format `SOURCE:DESTINATION[:FLAGS]`. Flags are optional and can include `ro`, `private`, etc.
+(ARRAY) List of bind mounts in the format `SOURCE:DESTINATION[:FLAGS]`. Flags are optional and can include `ro`, `private`, etc.
 
 !!! example
      * Literal fixed mount map
@@ -120,9 +120,9 @@ List of bind mounts in the format `SOURCE:DESTINATION[:FLAGS]`. Flags are option
     * Mount flags are separated with a plus symbol, for example: `ro+private`.
     * Optional flags from docker format or OCI (need reference)
 
-### (TABLE) env
+### env
 
-Environment variables to set in the container. Null-string values will unset the variable. Default: inherited from the host and the image.
+(TABLE) Environment variables to set in the container. Null-string values will unset the variable. Default: inherited from the host and the image.
 
 !!! example
      * Basic `env` block
@@ -145,9 +145,9 @@ Environment variables to set in the container. Null-string values will unset the
     * The env table can be used to further customize the container environment by setting, modifying, or unsetting variables.
     * Values of the table entries must be strings. If an entry has a null value, the variable corresponding to the entry key is unset in the container.
 
-### (TABLE) annotations
+### annotations
 
-OCI-like annotations for the container. For more details, refer to the [Annotations][ref-ce-annotations] section.
+(TABLE) OCI-like annotations for the container. For more details, refer to the [Annotations][ref-ce-annotations] section.
 
 !!! example