What delimiter separates instruction and comment in DETAIL EDIT?

• A. Hash #.
• B. Double slash //.
• C. Semicolon ;.
• D. Colon :

Answer: (B)

The idea being tested is how to mark inline comments so that human notes don’t affect the instruction. Using a double slash to start the comment portion is the best choice because it clearly signals that everything after it on the same line is a note or explanation, not executable instruction. This boundary lets the instruction remain valid while you add clarifying text.

Why this works well: the double slash is a widely recognized comment delimiter in many programming and scripting contexts, so readers immediately understand that the trailing text is for humans, not for the processor. It keeps the instruction clean and unambiguous while providing context or notes right alongside it.

Why the others don’t fit here: a hash is used for comments in several languages, but it’s not universally treated as an inline delimiter in this setup. a semicolon ends a statement rather than introducing a comment, so it wouldn’t reliably separate instruction from explanation. a colon is typically used to introduce lists, blocks, or key-value pairs, not to mark comments, so it wouldn’t consistently denote commentary either.