fix headers, reposition revised ideas

README.md

@@ -2,12 +2,12 @@
 [Web App UI Cleanup](#Web App UI Cleanup)
 
 
-[Completed Projects From Previous Years](#completed-projects-from-previous-years)
-
-[Profile and Optimize Purr Data for Realtime Safety](#profile-and-optimize-purr-data-for-realtime-safety)
+[Profile Purr Data CPU Usage in Realtime](#profile-purr-data-cpu-usage-in-realtime)
 
 [Terminal REPL](#terminal-repl)
 
+[Completed Projects From Previous Years](#completed-projects-from-previous-years)
+
 [Core Accessibility](#core-accessibility)
 
 [Purr Data Message and DSP Profiler](#purr-data-message-and-dsp-profiler)
@@ -61,8 +61,8 @@ You can find more information about our progress and TODOs from
 Javascript, HTML, CSS, and experience with SVG will be plus
 
 
-Profile and Purr Data CPU Usage in Realtime
--------------------------------------------
+Profile Purr Data CPU Usage in Realtime
+---------------------------------------
 
 ### Goal
 Give users the ability to visually and/or programmatically measure which DSP
@@ -80,10 +80,6 @@ It would be much better if there were a system-wide feature to give visual
 feedback to the user so they can find out which DSP objects are the most
 CPU-hungry.
 
-### Languages
-C for the backend, and HTML5 for the simple visualizations to show the user
-the results of performance measurements.
-
 ### Challenges
 The initial profiling will take some time but
 isn't particularly challenging. Making changes to the core audio engine,
@@ -91,7 +87,8 @@ however, will require some knowledge of Linux system interfaces and some of
 Purr Data's internals.
 
 ### Languages
-C, plus some HTML5 for simple visualization of the performance metrics
+C for the backend, and HTML5 for the simple visualizations to show the user
+the results of performance measurements.
 
 Terminal REPL
 -------------