docs: address writing feedback

Changes:
- Added the logo and graphical title at the top of README.md.
- Added a link to the GitHub releases in the README.md "Releases"
  section.
- Added links to [AWS Lambda](https://aws.amazon.com/lambda/) and
  [AWS Fargate](https://aws.amazon.com/fargate/) where they were
  mentioned.
- Harmonised the use of "built on" / "based on" / "uses" / "started
  from", "multitenant" vs "multi-tenant", and "microVM" vs "micro-VM"
  across all .md docs.
- Fixed some typos.

Signed-off-by: Radu Weiss <[email protected]>

Author: raduweiss

CHARTER.md

@@ -2,7 +2,7 @@
 
 ## Mission
 
-Enable secure, multi-tenant, minimal-overhead execution of container and
+Enable secure, multitenant, minimal-overhead execution of container and
 serverless workloads.
 
 ## Tenets (unless you know better ones)

FAQ.md

@@ -9,25 +9,27 @@ sufficient isolation between their applications when all containers have to use
 a shared operating system (OS) kernel. Containers offer fast startup times,
 while VMs offer hardware virtualization-based security boundaries that are more
 secure. Firecracker is a new virtualization technology that enables service
-owners to operate multi-tenant container-based services on bare metal machines
+owners to operate multitenant container-based services on bare metal machines
 by combining the speed, resource efficiency, and performance enabled by
 containers with the security and workload isolation properties of traditional
 VMs.
 
 ### Who developed Firecracker?
 
-Firecracker was built at Amazon Web Services to enable AWS services such as AWS
-Fargate and AWS Lambda to improve resource utilization and customer experience.
-Firecracker is based on Chromium OSs' Virtual Machine Monitor (crosvm), an
-open-sourced VMM written in Rust. Today, crosvm and Firecracker have diverged
-to serve very different customer needs. We plan to contribute back the bug fixes
-and tests added to shared crates, and any Firecracker functionality that's
-appealing for crosvm.
+Firecracker was built at Amazon Web Services to enable AWS services such as 
+[Lambda](https://aws.amazon.com/lambda/) and
+[Fargate](https://aws.amazon.com/fargate/) to improve resource utilization and
+customer experience. Firecracker started from Chromium OS's Virtual Machine
+Monitor (crosvm), an open-sourced VMM written in Rust. Today, crosvm and
+Firecracker have diverged to serve very different customer needs. We plan to
+contribute back the bug fixes and tests added to shared crates, and any
+Firecracker functionality that's appealing for crosvm.
 
 ### Who uses Firecracker today and how will they use Firecracker?
 
-Today, AWS Lambda and AWS Fargate are built on Firecracker. In the
-future, we plan to enable users to launch micro-VM backed containers
+Today, [AWS Lambda](https://aws.amazon.com/lambda/) and
+[AWS Fargate](https://aws.amazon.com/fargate/) are built on Firecracker. In the
+future, we plan to enable users to launch microVM backed containers
 via familiar interfaces such as containerd.
 
 ### Is Firecracker compatible with the container ecosystem such as Kubernetes, Docker, Kata containers?

README.md

@@ -1,6 +1,6 @@
-# Firecracker Read Me
+![Firecracker Logo Title](docs/fc-logo-title.png)
 
-Our mission is to enable secure, multi-tenant, minimal-overhead execution of
+Our mission is to enable secure, multitenant, minimal-overhead execution of
 container and serverless workloads.
 
 Read more about the Firecracker Charter [here](CHARTER.md).
@@ -14,33 +14,34 @@ machines, called microVMs, which combine the security and workload isolation
 properties of traditional VMs with the speed and resource efficiency of
 containers (you can create microVMs with any combination of vCPUs and memory).
 
-Firecracker implements a virtual machine monitor (VMM) based on the Linux Kernel
-Virtual Machine (KVM) to create and manage microVMs (there is one Firecracker
-process per microVM). Firecracker has a minimalist design. It excludes
-unnecessary devices and guest functionality to reduce the memory footprint and
-attack surface area of each microVM. This improves security, decreases the
-startup time, and increases hardware utilization. Firecracker currently supports
-Intel CPUs, with planned AMD and ARM support. Firecracker will also be
-integrated with popular container runtimes.
+Firecracker implements a virtual machine monitor (VMM) that uses the Linux
+Kernel Virtual Machine (KVM) to create and manage microVMs (there is one
+Firecracker process per microVM). Firecracker has a minimalist design. It
+excludes unnecessary devices and guest functionality to reduce the memory
+footprint and attack surface area of each microVM. This improves security,
+decreases the startup time, and increases hardware utilization. Firecracker
+currently supports Intel CPUs, with planned AMD and ARM support. Firecracker
+will also be integrated with popular container runtimes.
 
 Firecracker was developed at Amazon Web Services to accelerate the speed and
-efficiency of services like AWS Fargate and AWS Lambda. Firecracker is open
+efficiency of services like [AWS Lambda](https://aws.amazon.com/lambda/) and
+[AWS Fargate](https://aws.amazon.com/fargate/). Firecracker is open
 sourced under [Apache version 2.0](LICENSE).
 
 To read more about the benefits of Firecracker, check out
-[firecracker-microvm.io](firecracker-microvm.io).
+[firecracker-microvm.io](https://firecracker-microvm.github.io).
 
 ## Getting Started
 
 To try out Firecracker, go to the [quickstart guide](docs/getting-started.md).
 
-To enable service owners to run microVM-based containers in multi-tenant
+To enable service owners to run microVM-based containers in multitenant
 production fleets, we are working to integrate Firecracker in the container
 ecosystem; once this integration is complete, customers will be able to run
 pods, tasks, and containers within Firecracker microVMs.
 
 Service owners will also need to ensure that their host OS is configured to a
-security bar that enables safe multi-tenant computing. An configuration that we
+security bar that enables safe multitenant computing. A configuration that we
 consider meets this bar is included in
 [the production host setup document](docs/prod-host-setup.md).
 
@@ -56,7 +57,8 @@ To contribute to Firecracker, check out the development setup section in the
 
 ## Releases
 
-New Firecracker versions are released via GitHub's release infrastructure,
+New Firecracker versions are released via the GitHub repository
+[releases](https://github.com/firecracker-microvm/firecracker/releases) page,
 typically every one or two months. A history of changes is recorded in our
 [changelog](CHANGELOG.md).
 
@@ -92,7 +94,7 @@ The **API endpoint** can be used to:
   arguments.
 - Stop the microVM.
 
-**Build-in Capabilities**:
+**Built-in Capabilities**:
 
 - Demand fault paging and CPU oversubscription enabled by default.
 - Jailer process for starting Firecracker in production scenarios; applies a

docs/design.md

@@ -8,7 +8,7 @@ Firecracker is a new virtualization technology that enables customers to deploy
 lightweight *micro* Virtual Machines or microVMs. Firecracker microVMs combine
 the security and workload isolation properties of traditional VMs with the
 speed, agility and resource efficiency enabled by containers. They provide a
-secure, trusted environment for multi-tenant services, while maintaining
+secure, trusted environment for multitenant services, while maintaining
 minimal overhead.
 
 The scope of this document is to describe the features and architecture of the

docs/getting-started.md

@@ -18,8 +18,7 @@
 
 - **KVM**
 
-  Firecracker is built on top of [KVM](https://www.linux-kvm.org). Please make
-  sure that:
+  Firecracker uses [KVM](https://www.linux-kvm.org). Please make sure that:
   1. you have KVM enabled in your Linux kernel, and
   2. you have read/write access to `/dev/kvm`.
      If you need help setting up access to `/dev/kvm`, you should check out
@@ -290,4 +289,4 @@ test container and checking for net connectivity:
 ```bash
 docker pull alpine
 docker run --rm -it alpine ping -c 3 amazon.com
-```
+```