Add information about ct:comment to documentation

Author: Mikaka27

lib/common_test/doc/guides/ct_hooks_chapter.md

@@ -281,6 +281,22 @@ After any post hook has been executed for all installed CTHs,
 skipped, respectively. You cannot affect the outcome of the tests any further at
 this point.
 
+[](){: #comment }
+
+### Comment in hooks
+
+As mentioned in `ct:comment/1` same limitation regarding calling `ct:comment/1-2`
+exists in hook functions. Calling `ct:comment/1-2` should only be done directly from
+the process executing hook function, or it's descendant.
+
+Be aware that if you spawn a process in one hook function and keep it alive
+while common_test has moved to calling another hook function, and you try to
+execute `ct:comment/1-2` from this process the comment may not be printed in
+correct place in html logs, or at all.
+
+Calling this function from process that is neither a common_test process, nor it's
+descendant is no-op.
+
 [](){: #synchronizing }
 
 ## Synchronizing External User Applications with Common Test

lib/common_test/src/ct.erl

@@ -1055,6 +1055,20 @@ suite result page.
 
 If called several times, only the last comment is printed. The test case return
 value `{comment,Comment}` overwrites the string set by this function.
+
+> #### Warning {: .warning }
+>
+> This function (and `ct:comment/2`) should only be called from the process running
+> the common_test functions, typically the test case process or it's descendant.
+> Be aware that if you spawn a new process in one common_test function (e.g. `init_per_suite`)
+> and then execute `ct:comment/1-2` in that new process while the test execution has moved
+> to another common_test function (e.g. `init_per_testcase` or test case function) the comment
+> might not be printed in the correct place in html logs or at all.
+>
+> Calling this function from process that is neither a common_test process, nor it's
+> descendant is no-op.
+>
+> Similar limitation exists for common_test hooks, see: [Comment in hooks](ct_hooks_chapter.md#comment)
 """.
 -spec comment(Comment) -> ok
       when Comment :: term().