diff --git a/content/rancher/concepts/clusters/_index.md b/content/rancher/concepts/clusters/_index.md
index 3a559f2ec62..56cdd08836d 100644
--- a/content/rancher/concepts/clusters/_index.md
+++ b/content/rancher/concepts/clusters/_index.md
@@ -17,35 +17,33 @@ Coming Soon
 
 ### Node Components
 
-Coming Soon
+A Kubernetes cluster contains 3 types of nodes: etcd nodes, control plane nodes, and worker nodes.
 
-#### etcd Requirements
+#### etcd Nodes
 
-Coming Soon
+The etcd nodes are used to run the etcd database. etcd is a key value store used as Kubernetes’ backing store for all cluster data. Even though you can run etcd on a single node, you need 3, 5, or 7 nodes for redundancy.
 
-#### Control Requirements
+#### Control Plane Nodes
 
-Coming Soon
+The control plane nodes are used to run the Kubernetes API server, scheduler, and controller manager. Control plane nodes are stateless since all cluster data are stored on etcd nodes. You can run control plane on 1 node, although 2 or more nodes are required for redundancy. You can also run control plane on etcd nodes.
 
-#### Worker Requirements and Best Practices
+#### Worker Nodes
 
-Coming Soon
+Worker nodes are used to run the kubelet and the workload. It also runs the storage and networking drivers and ingress controllers when required. You create as many worker nodes as needed for your workload needs.
 
 ### Cluster Providers
 
-Coming Soon
+#### Rancher Kubernetes Engine (RKE)
 
-#### RKE
+RKE is Rancher’s own lightweight Kubernetes installer. It works with any cloud providers, virtualization platforms, or bare metal servers. It integrates with node drivers to automatically provision nodes on AWS, Azure, DigitalOcean, vSphere, OpenStack, etc. Users can add custom nodes to the cluster by running the Rancher agent on these nodes.
 
-Coming Soon
+#### Cloud-Managed Kubernetes Clusters
 
-#### Cloud Cluster
+Rancher integrates with cloud APIs so users can provision GKE, EKS, and AKS clusters directly from Rancher. New cloud managed Kubernetes clusters will be added as they become available.
 
-Coming Soon
+#### Imported Clusters
 
-#### Import
-
-Coming Soon
+Users can existing Kubernetes cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported Kubernetes clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clustered.
 
 ### Kubeconfig File
 
diff --git a/content/rancher/concepts/projects/_index.md b/content/rancher/concepts/projects/_index.md
index 81407df4cac..02b716e5e42 100644
--- a/content/rancher/concepts/projects/_index.md
+++ b/content/rancher/concepts/projects/_index.md
@@ -5,11 +5,9 @@ weight: 2150
 
 # Projects
 
-Coming Soon
-
 ## What's a Project?
 
-Coming Soon
+Project is a new concept introduced by Rancher. It is not a native Kubernetes construct. A project captures a set of policies for a set of namespaces. A user can be assigned a specific role in a project. A role can be owner, member, read-only, or custom. Policies include Kubernetes Role-Based Access Control (RBAC) policies and pod security policies. Rancher 2.0 also implements a canned network policy that isolated containers in different projects. Future version of Rancher will implement more flexible network policies.
 
 ### Authorization
 
@@ -21,4 +19,4 @@ Coming Soon
 
 ## Namespaces
 
-Coming Soon
+Kubernetes resources belong to specific namespaces. Rancher 2.0 relies on namespaces to isolate resources among users and apps. When the user deploys an app from the catalog, for example, he can choose to deploy that app into its own namespace, so that resource names in one app will not conflict with resource names in another. Namespaces must be globally unique. It is often difficult for users to pick unique namespace names. Rancher therefore encourages the pattern where users work with projects, and the system generates unique namespace names automatically.