Address code review feedback - clarify documentation

Co-authored-by: vlkale <11766050+vlkale@users.noreply.github.com>

Author: Copilot

docs/connectors/ScoreP.md

@@ -21,7 +21,7 @@ ScoreP is particularly valuable for:
 - Tracing communication and synchronization in distributed applications
 - Performance tuning of HPC applications
 
-Note: While ScoreP provides advanced tracing capabilities from a third-party library, it focuses on profiling and tracing rather than intelligent analysis or automatic tuning (unlike tools such as APEX).
+Note: While ScoreP provides advanced tracing capabilities as a third-party library, it focuses on profiling and tracing rather than intelligent analysis or automatic tuning (unlike tools such as APEX).
 
 ## Installation and Setup
 

docs/connectors/Timemory.md

@@ -128,7 +128,9 @@ timemory-roofline -t gpu_roofline \
 
 ## Output
 
-Output is located in `timemory-output/<DATE-TIME>` unless `KOKKOS_ROOFLINE` is set. The `<DATE-TIME>` format can be customized via `TIMEMORY_TIME_FORMAT` (default: `"%F_%I.%M_%p"`).
+Output is located in `timemory-output/<DATE-TIME>` by default. The `<DATE-TIME>` format can be customized via `TIMEMORY_TIME_FORMAT` (default: `"%F_%I.%M_%p"`).
+
+When using roofline analysis with `KOKKOS_ROOFLINE=ON`, the output location is controlled by the `TIMEMORY_OUTPUT_PATH` environment variable as shown in the roofline example above.
 
 Output formats include:
 - Console output (printed at end of application)