Add braces and udpdate readme

Author: aidangarske

README.md

@@ -162,5 +162,5 @@ To run the cipher suite testing:
 
 ## Debugging
 
-To enable wolfProvider debug logging, build with `--debug`. If you want to filter logging a certain way, set `WOLFPROV_LOG_LEVEL_FILTER` and `WOLFPROV_LOG_COMPONENTS_FILTER` in `include/wolfprovider/wp_logging.h` as needed. See comments in that file for examples.
+To enable wolfProvider debug logging, build with `--debug` which enables exit messages, error messages, and informational messages. If you want to filter logging a certain way or increase detail level, set `WOLFPROV_LOG_LEVEL_FILTER` and `WOLFPROV_LOG_COMPONENTS_FILTER` in `include/wolfprovider/wp_logging.h` as needed. See comments in that file for examples.
 

include/wolfprovider/wp_logging.h

@@ -262,7 +262,7 @@ void WOLFPROV_ERROR_FUNC_NULL_LINE(int type, const char* funcName,
 void WOLFPROV_BUFFER(int type, const unsigned char* buffer,
     unsigned int length);
 
-#else
+#else /* WOLFPROV_DEBUG */
 
 #define WOLFPROV_ENTER(t, m)
 #define WOLFPROV_LEAVE(t, m, r)

src/wp_logging.c

@@ -151,16 +151,19 @@ static void wolfprovider_log(const int logLevel, const int component,
                            const char *const logMessage)
 {
     /* Check compile-time configuration first */
-    if (!WOLFPROV_COMPILE_TIME_CHECK(component, logLevel))
+    if (!WOLFPROV_COMPILE_TIME_CHECK(component, logLevel)) {
         return;
+    }
 
     /* Don't log messages that do not match our current logging level */
-    if ((providerLogLevel & logLevel) != logLevel)
+    if ((providerLogLevel & logLevel) != logLevel) {
         return;
+    }
 
     /* Don't log messages from components that do not match enabled list */
-    if ((providerLogComponents & component) != component)
+    if ((providerLogComponents & component) != component) {
         return;
+    }
 
     if (log_function) {
         log_function(logLevel, component, logMessage);