Made changes as per latest suggestions.

Author: anvithks

content/en/docs/concepts/extend-kubernetes/poseidon-firmament-alternate-scheduler.md

@@ -6,9 +6,7 @@ weight: 80
 
 {{% capture overview %}}
 
-{{< note >}}
-	 Current release of Poseidon-Firmament scheduler is an alpha release.
-{{< /note >}}
+**Current release of Poseidon-Firmament scheduler is an <code> alpha </code> release.**
 
 Poseidon-Firmament scheduler is an alternate scheduler alongside the default Kubernetes scheduler. 
 
@@ -21,19 +19,19 @@ Poseidon-Firmament scheduler is an alternate scheduler alongside the default Kub
 
 Poseidon is the integration glue for the  [Firmament scheduler](https://github.com/Huawei-PaaS/firmament) with Kubernetes. Poseidon-Firmament scheduler augments the current Kubernetes scheduling capabilities. It incorporates novel flow network graph based scheduling capabilities alongside the default Kubernetes Scheduler. Firmament scheduler models workloads and clusters as flow networks and runs min-cost flow optimizations over these networks to make scheduling decisions.
 
-It models the scheduling problem as a constraint-based optimization over a flow network graph. This is achieved by reducing scheduling to a min-cost max-flow optimization problem. Due to the inherent rescheduling capabilities, the Poseidon-Firmament scheduler constantly keeps refining the workloads placements dynamically.  
+It models the scheduling problem as a constraint-based optimization over a flow network graph. This is achieved by reducing scheduling to a min-cost max-flow optimization problem. The Poseidon-Firmament scheduler dynamically refines the workload placements.  
 
 Poseidon-Firmament scheduler runs alongside the default Kubernetes Scheduler as an alternate scheduler – multiple schedulers running simultaneously. 
 
 ## Key Advantages
 
 ### Flow graph scheduling based Poseidon-Firmament scheduler provides the following key advantages:  
-- Workloads (pods) are bulk scheduled for enabling scheduling decisions at massive scale.  
+- Workloads (pods) are bulk scheduled to enable scheduling at massive scale..  
 - Based on the extensive performance test results, Poseidon-Firmament scales much better than Kubernetes default scheduler as the number of nodes increase in a cluster. This is due to the fact that Poseidon-Firmament is able to amortize more and more work across workloads.  
-- Poseidon-Firmament Scheduler outperforms K8S default scheduler by a wide margin when it comes to throughput performance numbers for scenarios where compute resource requirements are somewhat uniform across jobs (Replicasets/Deployments/Jobs). As shown in the graph below, Poseidon-Firmament scheduler end-to-end throughput performance numbers (including bind time) consistently get better and better as the number of nodes in a cluster increase. For example, for a 2,700 nodes cluster (shown in the graphs [here](https://github.com/kubernetes-sigs/poseidon/blob/master/docs/benchmark/README.md)), Poseidon-Firmament scheduler is 7X (or more) better end-to-end throughput-wise that includes bind time.     
+- Poseidon-Firmament Scheduler outperforms K8S default scheduler by a wide margin when it comes to throughput performance numbers for scenarios where compute resource requirements are somewhat uniform across jobs (Replicasets/Deployments/Jobs). Poseidon-Firmament scheduler end-to-end throughput performance numbers (including bind time) consistently get better and better as the number of nodes in a cluster increase. For example, for a 2,700 nodes cluster (shown in the graphs [here](https://github.com/kubernetes-sigs/poseidon/blob/master/docs/benchmark/README.md)), Poseidon-Firmament scheduler is 7X (or more) better end-to-end throughput-wise that includes bind time.     
 
 - Availability of complex rule constraints.  
-- Scheduling in Firmament is very dynamic; it keeps cluster resources in a global optimal state during every scheduling run.  
+- Scheduling in Poseidon-Firmament is dynamic; it keeps cluster resources in a global optimal state during every scheduling run.  
 - Highly efficient resource utilizations.  
 
 ## Poseidon-Firmament Scheduler - How it works	
@@ -60,14 +58,14 @@ As mentioned earlier, Poseidon-Firmament scheduler enables extremely high throug
 
 Although, Poseidon-Firmament scheduler is capable of scheduling various types of workloads (service, batch, etc.), following are the few use cases where it excels the most:  
 1. For “Big Data/AI” jobs consisting of large number of tasks, throughput benefits are tremendous.  
-2. Substantial throughput benefits also for service or batch job scenarios where workload resource requirements are uniform across jobs (Replicasets/Deployments/Jobs).  
+2. Service or batch jobs where workload resource requirements are uniform across jobs (Replicasets/Deployments/Jobs).  
 
 ## Current Project Stage	
 
 - **Alpha Release - Incubation repo.** at https://github.com/kubernetes-sigs/poseidon.  
 - Currently, Poseidon-Firmament scheduler **does not provide support for high availability**, our implementation assumes that the scheduler cannot fail. The [design document](https://github.com/kubernetes-sigs/poseidon/blob/master/docs/design/README.md) describes possible ways to enable high availability, but we leave this to future work.  
 - We are **not aware of any production deployment** of Poseidon-Firmament scheduler at this time.  
-- Poseidon-Firmament is supported  from Kubernetes release 1.6 and works with all subsequent releases.   
+- Poseidon-Firmament is supported from Kubernetes release 1.6 and works with all subsequent releases.   
 - The current Poseidon release is 0.6 and the corresponding Firmament release is 0.6.
 
 ## Features Comparison Matrix	
@@ -79,7 +77,7 @@ Although, Poseidon-Firmament scheduler is capable of scheduling various types of
 |Pod Affinity/Anti-Affinity - including support for pod anti-affinity symmetry|Y|Y|Currently, the default scheduler outperforms the Poseidon-Firmament scheduler pod affinity/anti-affinity functionality. We are working towards resolving this.|
 |Taints & Tolerations|Y|Y||
 |Baseline Scheduling capability in accordance to available compute resources (CPU & Memory) on a node|Y|Y**|Not all Predicates & Priorities are supported at this time.|
-|Extreme Throughput at scale|Y**|Y|This is due to Poseidon-Firmament bulk scheduling approach superiority versus K8S pod-at-a-time approach. Substantial throughput benefits using Firmament scheduler as long as resource requirements (CPU/Memory) for incoming Pods is uniform across Replicasets/Deployments/Jobs. This is mainly due to efficient amortization of work across Replicasets/Deployments/Jobs . 1) For “Big Data/AI” jobs consisting of large no. of tasks, throughput benefits are tremendous. 2) Substantial throughput benefits also for service or batch job scenarios where workload resource requirements are uniform across Replicasets/Deployments/Jobs.|
+|Extreme Throughput at scale|Y**|Y|Bulk scheduling approach scales or increases workload placement. Substantial throughput benefits using Firmament scheduler as long as resource requirements (CPU/Memory) for incoming Pods is uniform across Replicasets/Deployments/Jobs. This is mainly due to efficient amortization of work across Replicasets/Deployments/Jobs . 1) For “Big Data/AI” jobs consisting of large no. of tasks, throughput benefits are tremendous. 2) Substantial throughput benefits also for service or batch job scenarios where workload resource requirements are uniform across Replicasets/Deployments/Jobs.|
 |Optimal Scheduling|Pod-by-Pod scheduler, processes one pod at a time (may result into sub-optimal scheduling)|Bulk Scheduling (Optimal scheduling)|Pod-by-Pod K8S default scheduler may assign tasks to a sub-optimal machine. By contrast, Firmament considers all unscheduled tasks at the same time together with their soft and hard constraints.|
 |Colocation Interference Avoidance|N|N**|Planned in Poseidon-Firmament.|
 |Priority Pre-emption|Y|N**|Partially exists in Poseidon-Firmament versus extensive support in K8S default scheduler.|