Readme examples changes

Author: ekpatrice

examples/README.md

@@ -11,22 +11,25 @@ These are very simple projects where the application is basically one `while tru
 
 
 # How Pyroscope works
-Pyroscope is open-source software that allows you to continuously profile your code to debug performance issues down the line of code.
-If you haven't used profilers before, then welcome. 
-![pyroscope_diagram_no_logo-01](https://user-images.githubusercontent.com/23323466/104868724-1194d680-58f9-11eb-96da-c5a4922a95d5.png)
-If you are familiar with profiling / flamegraphs, then you should know that Pyroscope:
+Pyroscope identifies performance issues in your application by continuously profiling the code.
+
+If you've never used a profiler before, then welcome! 
+
+If you are familiar with profiling and flame graphs, then you'll be happy to know that Pyroscope:
 - Requires very minimal overhead
-- Is designed in a way that **it can store years of your applications perf data down to 10 second granularity.** 
-There are two main components that allow Pyroscope to do this:
+- Can store years of perf data down to 10 second granularity 
+- Uses a unique, inverted flame graph for increased readability
+
+There are two main components that allow Pyroscope to run smoothly and quickly:
 ## Pyroscope agent
-The Pyroscope agent wraps around your Python, Ruby, or Go application to poll the stacktrace (100 times per second) to calculate which function is consuming your CPU resources. 
-This simply means that 100 times a second Pyroscope records what function is currently using CPU to do some work or calculate something. 
+Every .01 seconds, the Pyroscope agent wraps around your Python, Ruby, or Go application to poll the stacktrace and calculate which function is consuming your CPU resources. 
+![pyroscope_diagram_no_logo-01](https://user-images.githubusercontent.com/23323466/104868724-1194d680-58f9-11eb-96da-c5a4922a95d5.png)
 ## Pyroscope Server
-Pyroscope records and aggregates what your application has been doing, it then sends that data to the Pyroscope server over port `:4040`
-Then here, the data is processed, aggregated, and stored ([BadgerDB](https://github.com/dgraph-io/badger)) in a way which allows for you to **quickly** query any time range:
+Pyroscope records and aggregates what your application has been doing, then sends that data to the Pyroscope server over port `:4040`([BadgerDB](https://github.com/dgraph-io/badger)) to be processed, aggregated, and stored  for speedy queries of any time range, including:
 - [x] all of 2020
-- [x] that one day that weird thing happened last month
-- [x] that time you deployed on a friday and everything went to s*** and nobody knew why
-- [x] A random 10 second span anytime ever that you only are querying to see if this is legit
-We've been running a demo in production for a while now.  Check out our [Demo Page](https://demo.pyroscope.io/) and select any time range to see how quick it is! 
+- [x] that one day last month when that weird thing happened
+- [x] that time you deployed on a Friday and messed up everything without knowing why
+- [x] A random 10 seconds you are only querying to see if Pyroscope is legit
+
+Check out our [Demo Page](https://demo.pyroscope.io/) and select any time range to see how quickly Pyroscope works! 
 ![image](https://user-images.githubusercontent.com/23323466/104861560-2ebfaa00-58e5-11eb-862e-3481f294cbcf.png)