Update resource-hook.md

Author: gwangmu

docs/software/container-engine/resource-hook.md

@@ -31,7 +31,7 @@ This can be done in multiple ways in TOML: for example, both of the following us
 
      * An assignment can implicitly define subtables if the key you assign is a dotted list. As a reference, see the examples made earlier in this section, where assigning a string to the `com.hooks.ssh.enabled` attribute within the `[annotations]` table is exactly equivalent to assigning to the `enabled` attribute within the `[annotations.com.hooks.ssh]` subtable.
 
-     * Attributes can be added to a table only in one place in the TOML file. In other words, each table must be defined in a single square bracket section. For example, Case 3 in the example below is invalid because the `ssh` table was doubly defined both in the `[annotations]` and in the `[annotations.com.hooks.ssh]` sections. See the [TOML format](https://toml.io/en/) spec for more details.
+     * Attributes can be added to a table only in one place in the TOML file. In other words, each table must be defined in a single square bracket section. See the [TOML format](https://toml.io/en/) spec for more details.
 
         ```bash title="Valid"
         [annotations.com.hooks.ssh]
@@ -49,9 +49,10 @@ This can be done in multiple ways in TOML: for example, both of the following us
         [annotations]
         com.hooks.ssh.authorize_ssh_key = "${SCRATCH}/tests/edf/authorized_keys"
 
-        [annotations.com.hooks.ssh]
+        [annotations.com.hooks.ssh]    # (1)
         enabled = "true"
         ```
+        1. The `ssh` table was doubly defined both in the `[annotations]` and in the `[annotations.com.hooks.ssh]` sections.
 
 ## Accessing native resources