fix image links

Author: David Kline (ANALOG)

Documentation/Diagnostics/UsingVisualProfiler.md

@@ -13,7 +13,7 @@ While developing an application, be sure to focus on multiple parts of the scene
 
 ## Visual Profiler Interface
 
-![Visual Profiler Interface](../../External/ReadMeImages/VisualProfiler.png)
+![Visual Profiler Interface](../../External/ReadMeImages/Diagnostics/VisualProfiler.png)
 
 The Visual Profiler interface includes the following components:
 
@@ -33,21 +33,26 @@ The specific platform and hardware configuration will play a significant role in
 
 ### Frame Time
 
-<< >>
+To the right of the frame rate is the frame time, in milliseconds, spent on the CPU. To achieve the target frame rates mentioned previously, an application can spend the following amount of time per frame:
+
+- 60 fps: 16.6 ms
+- 90 fps: 11.1 ms
+
+> GPU time is planned to be added in a future release.
 
 ### Frame Graph
 
 The frame graph provides a graphical display of the application frame rate history.
 
-![Visual Profiler Frame Graph](../../External/ReadMeImages/VisualProfilerMissedFrames.png)
+![Visual Profiler Frame Graph](../../External/ReadMeImages/Diagnostics/VisualProfilerMissedFrames.png)
 
 > When using the application, look for missed frames. Missed frames indicate the application is not hitting its target frame rate and may need optimization work.
 
 ### Memory Utilization
 
 The memory utilization display allows for easy understanding of how the current view is impacting an application's memory consumption. 
 
-![Visual Profiler Frame Graph](../../External/ReadMeImages/VisualProfilerMemory.png)
+![Visual Profiler Frame Graph](../../External/ReadMeImages/Diagnostics/VisualProfilerMemory.png)
 
 > When using application, look for total memory usage. Key indicators include: nearing the memory limit and rapid changes in usage.