Some typos and clarifications

Author: akshaisarma

docs/about/contact.md

@@ -14,7 +14,7 @@ If you have any issues with any of the particular Bullet sub-components, feel fr
 
 ## Mailing Lists
 
-If you have a general question, reach out to us at the Users list and at Developers if you have a particular question for the developers.
+If you have a general question, comment, or observation meant for general visibility, reach out to the Users list. If you want to keep it to just the developers, reach to that list instead.
 
 |            | Mail                                                                  | Forum                                                                                            |
 | ---------- | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |

docs/about/contributing.md

@@ -1,14 +1,14 @@
 # Contributing
 
-We welcome all contributions! We also welcome all usage experiences, stories, annoyances and whatever else you want to say. Head on over to our [Contact](contact.md) and let us know!
+We welcome all contributions! We also welcome all usage experiences, stories, annoyances and whatever else you want to say. Head on over to our [Contact Us page](contact.md) and let us know!
 
 ## Contributor License Agreement (CLA)
 
 Bullet is hosted under the [Yahoo Github Organization](https://github.com/yahoo). In order to contribute to any Yahoo project, you will need to submit a CLA. When you submit a Pull Request to any Bullet repository, a CLABot will ask  you to sign the CLA if you haven't signed one already.
 
 ## Future plans
 
-Here is a list of features we are currently considering/working on. If the Status column is empty, we are still discussing how to approach/break them. They will be updated as they are solidified. Feel free to [contact us](contact.md) with any ideas/suggestions/PRs! 
+Here is a list of features we are currently considering/working on. If the Status column is empty, we are still discussing how to prioritize/approach/break them down. They will be updated as they are solidified. Feel free to [contact us](contact.md) with any ideas/suggestions/PRs!
 
 This list is neither comprehensive nor in any particular order.
 

docs/quick-start.md

@@ -16,7 +16,7 @@ By the following the steps in this section, you will:
 
 ## Setting up Storm
 
-To set up a clean working environment, let's start with setting some directories.
+To set up a clean working environment, let's start with creating some directories.
 
 #### Step 1: Setup directories and examples
 
@@ -84,7 +84,7 @@ storm kill topology
 
 !!! note "Local mode cleanup"
 
-    If you notice any problems while setting up storm or while relaunching a topology, it may be because some state is corrupted. When running Storm in this fashion, states and serializations are stored in ```storm-local```. You may want to ```rm -rf storm-local/*``` to remove everything in this directory before relaunching Storm components.
+    If you notice any problems while setting up storm or while relaunching a topology, it may be because some state is corrupted. When running Storm in this fashion, states and serializations are stored in ```storm-local``` and ```/tmp/```. You may want to ```rm -rf storm-local/* /tmp/dev-storm-zookeeper``` to clean up this state before relaunching Storm components. See the [tear down section](#teardown) on how to kill any running instances.
 
 ## Setting up the example Bullet topology
 
@@ -214,15 +214,15 @@ To cleanup all the components we bought up:
 | Web Service    | ```ps aux | grep [e]xample_context.properties | awk '{print $2}' | xargs kill```    |
 | Storm          | ```ps aux | grep [a]pache-storm-1.0.3 | awk '{print $2}' | xargs kill```            |
 
-You can also ```rm -rf $BULLET_HOME /tmp/dev-storm-zookeeper /tmp/jetty-*``` to clean up your file system too.
+You can also ```rm -rf $BULLET_HOME /tmp/dev-storm-zookeeper /tmp/jetty-*``` to delete *everything* that we did so far.
 
 ## What did we do?
 
-This section will cover the various custom pieces this example plugged into Bullet, so you can better understand what we did.
+This section will go over the various custom pieces this example plugged into Bullet, so you can better understand what we did.
 
 ### Storm topology
 
-The topology was the Bullet topology plugged in with a custom spout. This spout is implemented in this [example project](https://github.com/yahoo/bullet-docs/blob/master/examples/storm/) was already built for you when you [downloaded the examples](#step-1-setup-directories-and-examples). This spout produces a maximum number of records in a given period. Both these arguments are configurable. If you examine $BULLET_HOME/backend/storm/launch.sh, you'll see the following:
+The topology was the Bullet topology plugged in with a custom spout. This spout is implemented in this [example project](https://github.com/yahoo/bullet-docs/blob/master/examples/storm/) and was already built for you when you [downloaded the examples](#step-1-setup-directories-and-examples). It does not read from any data source and just produces random, structured data. It also produces only up to a maximum number of records in a given period. Both this maximum and the length of a period are configurable. If you examine $BULLET_HOME/backend/storm/launch.sh, you'll see the following:
 
 ```bash
 storm jar bullet-storm-example-1.0-SNAPSHOT-jar-with-dependencies.jar \

docs/ui/usage.md

@@ -158,3 +158,9 @@ In this example, we group by ```tuple_number```. Recall that this is the number
 !!! note "Why no Count Distinct after Grouping"
 
     At this time, we do not support counting distinct values per field because with the current implementation of Grouping, it would involve storing Data Sketches within Data Sketches. We are considering this in a future release however.
+
+!!! note "Aha, sorting by tuple_number didn't sort properly!"
+
+    Good job, eagle eyes! Unfortunately, whenever we group on fields, those fields become strings under the current implementation. Rather than convert them back at the end, we have currently decided to leave it as is. This means that in your results, if you try and sort by a grouped field, it will perform a lexicographical sort.
+
+    This also means that you can actually group by any field - including non primitives such as maps and lists! The field will be converted to a string and that string will be used as the field's representation for uniqueness and grouping purposes.