Comment updates

Author: feasel0

build/chip/chip_test_suite.gni

@@ -72,6 +72,7 @@ template("chip_test_suite") {
   #++++x did we change the logic here?  think about it for all cases that don't involve building efr32 test driver -- would should happen if chip_link_tests is true or false?
   #   prior to me making my changes for efr32 test driver, was it was ok if the the test_sources were contained in both the common library and the individual libraries?
 
+  # Target for the common library.  Contains all the common sources, and sometimes all the individual test sources.
   if (chip_build_test_static_libraries) {
     _target_type = "static_library"
   } else {
@@ -96,6 +97,8 @@ template("chip_test_suite") {
       public_deps += [ "${chip_root}/src/platform/logging:default" ]
     }
   }
+
+  # Build a source_set or a flashable executable for each individual unit test source, which also includes the common files.
   if (chip_link_tests || pw_test_builds_executable) {
     tests = []