diff --git a/docker-store/certify-plugins-logging.md b/docker-store/certify-plugins-logging.md
index 4022f4e44a..60b1eb8a33 100644
--- a/docker-store/certify-plugins-logging.md
+++ b/docker-store/certify-plugins-logging.md
@@ -14,6 +14,8 @@ This page explains how publishers can successfully test their **Docker logging p
 
 > Content that requires a non-certified infrastructure environment cannot be published as certified.
 
+> You should perform this Self Certification test prior to submitting your product for publishing.
+
 ## Certify your logging plugins
 
 You must use the tool, `inspectDockerLoggingPlugin`, to certify your content for publication on Docker Store by ensuring that your Docker logging plugins conform to best practices.
@@ -28,6 +30,8 @@ The `inspectDockerLoggingPlugin` command verifies that your Docker logging plugi
 
 - Displays the container logs and compares it to `quotes.txt`. If they match, the test is successful.
 
+> The `inspectDockerLoggingPlugin` tool will detect issues and output them as **warnings** or **errors**. **Errors** must be fixed in order to certify. Resolving **warnings** is not required to certify, but you try to resolve them.
+
 The syntax for running a specific logging plugin is: `docker container run --log-driver`.
 
 No parameters are passed to the logging plugin. If parameters are required for the Docker logging plugin to work correctly, then a custom test script must be written and used. The default `docker container run` command is: