Tiny spelling mistake fix in FAQ (#2448)

Co-authored-by: Benjamin Raskin <[email protected]>

docs/faqs/index.md

@@ -20,7 +20,7 @@ Yes it stores the data (i.e. the timeseries datapoints) as well as the tags sinc
 
 - **How are writes handled and how is the data kept consistent within M3DB?**
 M3 uses quorum/majority consistency to ensure data is written to replicas in a way that can be read back consistently. 
-For example, if you have a replication factor of 3 and your set your write and read consistencies to quorum, then all writes will only succeed if they make it to at least 2 of the 3 replicas, and reads will only succeed if they get results back from at least 2 of the 3 replicas
+For example, if you have a replication factor of 3 and you set your write and read consistencies to quorum, then all writes will only succeed if they make it to at least 2 of the 3 replicas, and reads will only succeed if they get results back from at least 2 of the 3 replicas
 
 - **Do I need to restart M3DB if I add a namespace?**
 If you’re adding namespaces, the m3dbnode process will pickup the new namespace without a restart.
@@ -73,4 +73,4 @@ TBA
 Refer to the [Namespace configuration guide](../operational_guide/namespace_configuration.md).
 
 - **How can I see the cardinality of my metrics?**
-Currently, the best way is to go to the [M3DB Node Details Dashboard](https://grafana.com/grafana/dashboards/8126) and look at the `Ticking` panel. However, this is not entirely accurate because of the way data is stored in M3DB -- time series are stored inside time-based blocks that you configure. In actuality, the `Ticking` graph shows you how many unique series there are for the most recent block that has persisted. In the future, we plan to introduce easier ways to determine the number of unique time series. 
+Currently, the best way is to go to the [M3DB Node Details Dashboard](https://grafana.com/grafana/dashboards/8126) and look at the `Ticking` panel. However, this is not entirely accurate because of the way data is stored in M3DB -- time series are stored inside time-based blocks that you configure. In actuality, the `Ticking` graph shows you how many unique series there are for the most recent block that has persisted. In the future, we plan to introduce easier ways to determine the number of unique time series.