Update faq.md (#197)

Update FAQ with the general section

reference/faq.md

@@ -1,29 +1,60 @@
-# Frequently Asked Questions \(FAQ\)
+# Frequently Asked Questions (FAQ)
 
-If there is something you'd like to see in here that isn't already, please reach out \(_link to channels_\) to one of the mods and we'll get it added!
+If there is something you'd like to see in here that isn't already, please reach out (_link to channels_) to one of the mods and we'll get it added!
 
-### Table of Contents
+### Table of Contents  
+[General](#General)  
+[Product](#Product)  
+[Supermini](#Supermini)  
 
-[Product](faq.md#Product)  
-[Supermini](faq.md#Supermini)
+<a name="General"/>
+
+## General
+
+**What is the core value prop of Akash network?**
+
+Besides being self-sovereign, permission-less, and decentralized, Akash is a reverse auction marketplace - Airbnb for Compute. Unlike Airbnb or centralized cloud providers however, the **Tenant** ("guests" in Airbnb terms) has the power to decide what to pay, when, and filter the provider via audited attributes. The Provider bids on the Tenants' workload to run on their compute. Tenants have predictability on what it will cost, at all times, because the power in their hands.
+
+The core value of Akash is the ability for the Tenant (owner of the workloads) to set the price **_and_** the terms. The Tenant _decides_. They don't have to be surprised by the sticker shock of a monthly billing cycle.
+
+Most customers don't know _why_ they are paying what they are paying. Now, they know because they decide.
+
+Anyone can become a provider on our network.
+
+**How does the Akash Network compete against the AWS spot instances in terms of price?**
+
+Spot Instances are exactly the same as On-Demand Instances. However, Spot does not guarantee that you can keep your running instances long enough to finish your workloads. Spot also does not guarantee that you can get immediate availability of the instances that you are looking for, or that you can always get the aggregate capacity that you requested. Moreover, Spot Instance interruptions and capacity can change over time because Spot Instance availability varies based on supply and demand, and past performance isn’t a guarantee of future results.
+
+Spot Instances are not suitable for workloads that are inflexible, stateful, fault-intolerant, or tightly coupled between instance nodes. It's not recommended for workloads that are intolerant of occasional periods when the target capacity is not completely available. 
+
+Generally, it is cheaper to run on Akash and will be for the foreseeable future, especially, when we introduce fractional uAKT. However, pricing is on a continuum. It's variable, and dynamic at any given time. In Airbnb terms - a hut to a luxury villa. 
+
+<a name="Product"/>
 
 ## Product
 
+**Where do I start?**
+
+- To deploy [locally](https://github.com/ovrclk/akash)
+- To [learn and deploy](https://docs.akash.network/) on _Testnet and/or Mainnet_
+
 **Can Akash provide Name Server Services?**
 
-One issue with using name servers is that DNS will be exposed on a random ephemeral port instead of 53. We have plans to add IP addresses as a resource of the lease but it is not available yet.
+One issue with using name servers is that DNS will be exposed on a random ephemeral port instead of 53.  We have plans to add IP addresses as a resource of the lease but it is not available yet.
 
 **Do I need to redeploy if I want to update the deployment?**
 
-It depends what you'd like to update. Akash Groups are translated into Kubernetes Deployments, this means that only a few fields from the Akash SDL are mutable. For example image, command, args, env and exposed ports can be modified, but compute resources and placement criteria cannot.
+It depends what you'd like to update. Akash Groups are translated into Kubernetes Deployments, this means that only a few fields from the Akash SDL are mutable. 
+For example image, command, args, env and exposed ports can be modified, but compute resources and placement criteria cannot.
 
-**How can I \(someone wanting to deploy an application on Akash\) be sure that the provider won't/didn't try to modify my application?**
+**How can I (someone wanting to deploy an application on Akash) be sure that the provider won't/didn't try to modify my application?**
 
-At this time we don't have secure enclave support. There are some technical limitations to TEE and the like. Our audited attributes system is meant to approach the problem from a different angle. Why would you trust digital ocean, or aws, or any other cloud provider in the first place? some metric of trust. The audited attributes feature allows you to deploy only to providers that have been "signed off" on by an entity that you have confidence in.
+At this time we don't have secure enclave support.  There are some technical limitations to TEE and the like. Our audited attributes system is meant to approach the problem from a different angle.
+Why would you trust digital ocean, or aws, or any other cloud provider in the first place? some metric of trust. The audited attributes feature allows you to deploy only to providers that have been "signed off" on by an entity that you have confidence in. 
 
-**Is there also a way to decentralize docker registry? So it would not be a single point of failure, if selected one \(centralized\) goes down?**
+**Is there also a way to decentralize docker registry? So it would not be a single point of failure, if selected one (centralized) goes down?**
 
-Yes, this is something we've talked about for a long time but haven't had a chance to dig into much. It could be a bittorrent-style thing or it could be on IPFS, etc... We intend to explore all of this but we're focusing on getting people onto the platform with the assumption that their docker containers are more or less reachable for the time being.
+Yes, this is something we've talked about for a long time but haven't had a chance to dig into much.  It could be a bittorrent-style thing or it could be on IPFS, etc... We intend to explore all of this but we're focusing on getting people onto the platform with the assumption that their docker containers are more or less reachable for the time being.
 
 **Are there plans to add support for persistent volumes?**
 
@@ -37,13 +68,15 @@ It is on the roadmap, however, GPU workloads aren't supported just yet - there a
 
 Images need to be publicly accessible at this time.
 
+
+<a name="Supermini"/>
+
 ## Supermini
 
 **When can I get the Supermini and can it be shipped outside the US?**
 
-Currently there is no further information about the supermini, its availability in the US and Europe, or dates of availability for subsequent orders. In the meantime, feel free to sign up to the waitlist! [https://akash.network/supermini/](https://akash.network/supermini/)
+Currently there is no further information about the [supermini](https://akash.network/supermini), its availability in the US and Europe, or dates of availability for subsequent orders. 
 
 **How much money can the Supermini make me?**
 
 The yield from running a Supermini as a provider on the Akash Network will be a function of demand/network usage - meaning it will depend on how many applications are being deployed on the network. We are focused on on building this demand over the coming months.
-