fix(docs): re-format markdown files

src/docs/ocean/features/launch-specifications.md

@@ -55,5 +55,6 @@ For example, you could use the Labels and Taints attributes to instruct Ocean wh
 In addition, you can initiate a roll per VNG. This is useful when you need to apply changes to a VNG or restart the VNG for any reason without impacting other instances in the Ocean cluster. For more information, see [Initiate Roll per launchSpecIds](https://docs.spot.io/api/#operation/oceanAwsRollInit).
 
 ## What’s next?
-* Learn how to [Manage Virtual Node Groups](ocean/tutorials/manage-virtual-node-groups.md).
-* Learn more about the VNGs in the APIs: [AWS Kubernetes](https://docs.spot.io/api/#operation/OceanAWSClusterCreate), [ECS](https://docs.spot.io/api/#operation/OceanECSClusterCreate), [GKE](https://docs.spot.io/api/#operation/OceanGKEClusterCreate)
+
+- Learn how to [Manage Virtual Node Groups](ocean/tutorials/manage-virtual-node-groups.md).
+- Learn more about the VNGs in the APIs: [AWS Kubernetes](https://docs.spot.io/api/#operation/OceanAWSClusterCreate), [ECS](https://docs.spot.io/api/#operation/OceanECSClusterCreate), [GKE](https://docs.spot.io/api/#operation/OceanGKEClusterCreate)

src/docs/ocean/features/right-sizing.md

@@ -25,8 +25,9 @@ The output produces a single point in time data point for each pod. Ocean then a
 The aggregation is made twice to include both maximum and mean resource utilization values (e.g., max_memory_utilization and mean_memory_utilization), which will be used in the recommendation generation process to ensure that each pod’s utilization is considered properly.
 
 Using the per-workload aggregated data points, Ocean makes recommendations based on a mechanism that tries to even out peaks and troughs in resource demand.
-* Recommendations for decreasing resource requests are based on the above calculation using the maximum resource utilization data collected (e.g., max_memory_utilization).
-* Recommendations for increasing resource requests are based on the above calculation using the mean resource utilization data collected (e.g., mean_memory_utilization).
+
+- Recommendations for decreasing resource requests are based on the above calculation using the maximum resource utilization data collected (e.g., max_memory_utilization).
+- Recommendations for increasing resource requests are based on the above calculation using the mean resource utilization data collected (e.g., mean_memory_utilization).
 
 Currently, Ocean generates recommendations for Kubernetes deployments, statefulsets, and daemonsets.
 

src/docs/ocean/tutorials/manage-virtual-node-groups.md

@@ -9,7 +9,8 @@ This tutorial describes how to create, view, edit, and delete VNGs in Ocean.
 The following procedures are relevant for users of Ocean Kubernetes on AWS.
 
 ## Prerequisites
-* An Ocean cluster up and running
+
+- An Ocean cluster up and running
 
 ## Create a VNG
 
@@ -30,35 +31,39 @@ This procedure describes how to create a VNG from scratch.
 <img src="/ocean/_media/tutorials-manage-vngs-02a.png" width="518" height="400" />
 
 ## Configuration Parameters
-* Name: The name you assign to the new VNG.
-* Image: The Amazon machine image (AMI) used for the VNG.
-* Security Groups: The security groups that apply to the VNG. You can choose up to five groups as per the [AWS limitation](https://docs.aws.amazon.com/vpc/latest/userguide/amazon-vpc-limits.html#vpc-limits-security-groups).
-* Subnets: The subnets that apply to the VNG. You can choose multiple subnets.
-* Root Volume Size: The root volume size in GiB. This field and blockDeviceMappings cannot be used in the same VNG.
-* Instance Profile: The iamRole object applicable to the instance profile.
-* User Data (Startup Script): The user data script to be set in Base64-encoded MIME.
+
+- Name: The name you assign to the new VNG.
+- Image: The Amazon machine image (AMI) used for the VNG.
+- Security Groups: The security groups that apply to the VNG. You can choose up to five groups as per the [AWS limitation](https://docs.aws.amazon.com/vpc/latest/userguide/amazon-vpc-limits.html#vpc-limits-security-groups).
+- Subnets: The subnets that apply to the VNG. You can choose multiple subnets.
+- Root Volume Size: The root volume size in GiB. This field and blockDeviceMappings cannot be used in the same VNG.
+- Instance Profile: The iamRole object applicable to the instance profile.
+- User Data (Startup Script): The user data script to be set in Base64-encoded MIME.
 
 ### Node Selection Parameters
 
 This section enables you to inform Ocean about the labels and taints that are set on the nodes. When they are set, Ocean will use them to choose the right VNG for a pending pod.
-* Node Labels: Key/Value pairs defined on the Kubernetes nodes.
-* Node [Taints](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/): Triplets of Key, Value, and Effect defined on the Kubernetes nodes.
+
+- Node Labels: Key/Value pairs defined on the Kubernetes nodes.
+- Node [Taints](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/): Triplets of Key, Value, and Effect defined on the Kubernetes nodes.
 
 ---
+
 **Tip**: Be sure to label your instances according to your label selection:
 For Kubernetes user data, see [Create Custom Labels](https://docs.spot.io/ocean/tutorials/create-custom-labels).
 
 ---
 
 ## Advanced Parameters
-* Maximum Nodes: The upper limit number of instances that you can scale up to.
-* Block Device Mapping: Block devices that are exposed to the instance. You can specify virtual devices and EBS volumes. This parameter and rootVolumeSize cannot be in the spec at the same time.
-* Tags: Key and Value pairs used to apply tags on the EC2 machine. Specific tags can be applied per VNG.
-* Headroom: Spare resource capacity management enabling fast assignment of Pods without waiting for new resources to launch.
-* Reserve: The number of units to retain as headroom, where each unit has the defined headroom CPU and memory.
-* CPU (millicpu): Optionally configure the number of CPUs to allocate to the headroom. CPUs are denoted in millicores, where 1000 millicores = 1 vCPU.
-* Memory (MiB): Optionally configure the amount of memory (MiB) to allocate to the headroom.
-* GPUs: Optionally configure the number of GPUs to allocate for headroom unit.
+
+- Maximum Nodes: The upper limit number of instances that you can scale up to.
+- Block Device Mapping: Block devices that are exposed to the instance. You can specify virtual devices and EBS volumes. This parameter and rootVolumeSize cannot be in the spec at the same time.
+- Tags: Key and Value pairs used to apply tags on the EC2 machine. Specific tags can be applied per VNG.
+- Headroom: Spare resource capacity management enabling fast assignment of Pods without waiting for new resources to launch.
+- Reserve: The number of units to retain as headroom, where each unit has the defined headroom CPU and memory.
+- CPU (millicpu): Optionally configure the number of CPUs to allocate to the headroom. CPUs are denoted in millicores, where 1000 millicores = 1 vCPU.
+- Memory (MiB): Optionally configure the amount of memory (MiB) to allocate to the headroom.
+- GPUs: Optionally configure the number of GPUs to allocate for headroom unit.
 
 ## Example 1: Run a Windows Node in a Linux Cluster
 
@@ -81,8 +86,10 @@ spec:
 ```
 
 2. Configure your Ocean cluster with a VNG that serves the WinPod nodeSelector label. (See the steps above in [Create a VNG](ocean/tutorials/manage-virtual-node-groups?id=create-a-vng).)
+
    1. In the VNG configuration, set the image to Windows OS.
    2. In the VNG configuration, go to Node Selection and define the following node label:
+
       ```
       Key: runOnWin
       Value: true
@@ -105,6 +112,7 @@ You don't need to add any extra label for GPU support. You can use taints that r
 ## Create a VNG from an ASG
 
 The following procedure describes how to create a VNG in an Ocean cluster using the configuration from an existing Amazon autoscaling group. This process is referred to as importing a VNG from an ASG.
+
 1. In the console, go to Ocean/Cloud Clusters and click the Cluster Name you want to add a VNG to.
 2. In the summary page for the cluster, click Virtual Node Groups.
 3. Click Create New Virtual Node Group.
@@ -118,6 +126,7 @@ The following procedure describes how to create a VNG in an Ocean cluster using
 ## View VNGs
 
 Ocean provides a dashboard that enables you to track live data per VNG. You can review the resource allocation, number of nodes and pods running, and other information about the VNGs.
+
 1. In the console, go to Ocean/Cloud Clusters and click the Cluster you want to add a VNG to.
 2. Click the Virtual Node Groups tab. The Virtual Node Groups tab opens and displays a summary of all the VNGs defined in the Ocean cluster.
 
@@ -126,15 +135,16 @@ Ocean provides a dashboard that enables you to track live data per VNG. You can
 ### VNG Summary Table
 
 The VNG summary table can display the following columns:
-* ID: The identification code of the VNG.
-* Name: The user-defined name of the VNG. (If a VNG was defined without a time, it will appear in this column as Unnamed Virtual Node Group.)
-* Resource Allocation: Percent of defined resources (CPU, Memory, and GPU) currently used by the VNG.
-* Running Pods: Number of pods the VNG currently uses.
-* Nodes: Number of nodes the VNG currently uses.
-* Node Labels: Number of node labels the VNG uses.
-* Node Taints: Number of taints the VNG uses.
-* Tags: Number of tags the VNG uses.
-* Max Nodes: The maximum number of nodes defined for the VNG.
+
+- ID: The identification code of the VNG.
+- Name: The user-defined name of the VNG. (If a VNG was defined without a time, it will appear in this column as Unnamed Virtual Node Group.)
+- Resource Allocation: Percent of defined resources (CPU, Memory, and GPU) currently used by the VNG.
+- Running Pods: Number of pods the VNG currently uses.
+- Nodes: Number of nodes the VNG currently uses.
+- Node Labels: Number of node labels the VNG uses.
+- Node Taints: Number of taints the VNG uses.
+- Tags: Number of tags the VNG uses.
+- Max Nodes: The maximum number of nodes defined for the VNG.
 
 You can change the sort order in the table by clicking on the column headings.
 
@@ -153,10 +163,12 @@ Use the search box to filter items in the table or search for a specific VNG.
 To see the configuration details of a VNG, click on the Name of the VNG.
 
 ## Edit a VNG
+
 1. To edit the configuration of a VNG, go to the Virtual Node Groups tab and click on the Name of the VNG.
 2. Make the required changes in the configuration and click Save.
 
 ## Delete a VNG
+
 1. To delete a VNG, go to the Virtual Node Groups tab.
 2. In the VNG summary table, mark the VNG(s) to delete and click Delete.