fix(orka-engine): fix truncated Key Concepts and misaligned feature list

orka/orka-engine/orka-engine-30.mdx

@@ -10,28 +10,26 @@
 
   * A host (or node) is a physical computer with a host macOS and an installation of Orka Engine.
   * An image is the bits on disk representing a VM that can be used for saving state and sharing.
-  * MacStadium base VM Orka images are macOS OCI compliant VM images stored in our public GitHub registry [ghcr.io/macstadium/orka-images/](http://ghcr.io/macstadium/orka-images/) with user credentials user/pwd:
+  * MacStadium base VM Orka images are macOS OCI compliant VM images stored in our public GitHub registry [ghcr.io/macstadium/orka-images/](http://ghcr.io/macstadium/orka-images/). Default VM credentials: **admin** / **admin**.
 
 
 
 ## What’s in the Release
 
   * Deploy Orka Engine on an Apple silicon host on private or public infrastructure via a Command Line Interface (CLI).
-
-* List Virtual Machines and running status
-* Restart Virtual Machines
-* Stop Virtual Machines
-* Clone Virtual Machine images
-* Edit Virtual Machine settings for (Ex. CPUs, Mem, Display Resolution, Dots Per Inch)
-* Delete Virtual Machines
-* Save Virtual Machines
-* Push VMs to Open Container Initiative (OCI) compliant registry
-* Pull VMs from OCI registry
-* List available VM images on local file system
-* Copy VMs on local file system
-* Delete VMs from local file system
-* Create and deploy Orka OCI compliant Virtual Machine images.
-
+    * List Virtual Machines and running status
+    * Restart Virtual Machines
+    * Stop Virtual Machines
+    * Clone Virtual Machine images
+    * Edit Virtual Machine settings (CPUs, Memory, Display Resolution, DPI)
+    * Delete Virtual Machines
+    * Save Virtual Machines
+    * Push VMs to OCI-compliant registry
+    * Pull VMs from OCI registry
+    * List available VM images on local file system
+    * Copy VMs on local file system
+    * Delete VMs from local file system
+    * Create and deploy Orka OCI compliant VM images
   * Deploy headless VMs (no display console)
 
 
@@ -50,7 +48,7 @@
 
 Orka Engine requires a valid license key to operate. To request a license key:
 
 1. Contact your MacStadium account representative
 
 2. Provide your organization name, deployment details, and use case
 
@@ -66,9 +64,9 @@
 
 To install Orka Engine on an Apple silicon ARM (M1-M3) computer running macOS 13 (Ventura) and above, it is necessary to acquire and run the installer package.
 
 The Orka Engine installer is self-guided and takes less than a minute to install successfully. Simply double click or right click open the **orka-engine.pkg** file from the source download directory and follow the prompts.
 
 ![macOS installer window for orka-engine showing the Introduction step](/images/attachments/39594591423515.png)
 
 ![Orka Engine app icon showing an orca whale with a terminal prompt symbol](/images/attachments/39594527742107.png)
 
@@ -83,7 +81,7 @@
   * Save that VM as an image using `orka-engine vm save`
   * Listing images available on disk with `orka-engine image list`
   * Stop a VM with **ctrl-c** in terminal window bound to running VM or by closing the Dock item
   * Run a base template VM image hosted from MacStadium using `orka-engine vm run`
     * `orka-engine vm run latest-sonoma --image ghcr.io/macstadium/orka-images/sonoma:latest`
   * Pulling remote images locally using `orka-engine image pull`
   * Starting a VM in the stopped state with `orka-engine vm start`
@@ -95,7 +93,7 @@
 
 After Orka Engine is installed, open a terminal window. The command `orka-engine` is installed at `/usr/local/bin/orka-engine` \- this should be in the $PATH for most users by default.
 
 ## Using orka-engine --help
 
 The `orka-engine --help` command lists the three subcommands, `vm`to manage VMs, `image` to manage images, and `host` to see information about the host.
 
@@ -113,7 +111,7 @@
 ```
 orka-engine vm run latest-ipsw --ipsw latest --disk-size 90
 ```
 `orka-engine vm run` is a blocking function. Open another terminal window to interface with orka-engine for other functions while the VM is running. Stop a VM with **ctrl-c** or via the UI window **Menu - > Quit**.
 
 ## Common Options when Running a VM
 
@@ -160,7 +158,7 @@
 
 Orka engine can list the name and resource consumption of VMs that are currently running or stopped on a local host.
 
 ![Terminal output of orka-engine vm list showing a VM named latest-ipsw with 2 CPUs, 4096M memory, in running state](/images/attachments/39594527745947.png)
 
 ## Saving a VM as an Image
 
@@ -168,7 +166,7 @@
 
 For example,`orka-engine vm save latest-ipsw sonoma146-vanilla` saves the VM called `latest-ipsw` as an image with the name **sonoma146-vanilla**
 
 ![Terminal confirmation: The image 'sonoma146-vanilla' for VM 'latest-ipsw' has been successfully saved](/images/attachments/39594591426971.png)
 
 ## Listing Images Available on Disk
 
@@ -178,9 +176,9 @@
 
 Stop a headless VM or VM with a display console enter **ctrl-c**(from the terminal window VM was started with) or if deployed with a display console, by choosing the apple icon in the VM and selecting Shut Down… .
 
 ## Running a VM Based on a MacStadium Hosted Image
 
 MacStadium hosts a number of Sequoia, Sonoma, and Ventura images on [GitHub - macstadium/orka-images: Public images for Apple silicon-based Orka virtual machines](https://github.com/macstadium/orka-images/) In `orka-engine vm ,` specify an `--image` option to be the URL of an image coming from an OCI registry, 
 
 ```bash
 orka-engine vm run sonoma-latest --image ghcr.io/macstadium/orka-images/sonoma:latest
@@ -197,7 +195,7 @@
 
 
 
 ## Reviewing Current List of VMs (in VMs orka-engine)
 
 It is now possible to start a second terminal and run `orka-engine vm list`, and the following output appears, (which indicates that the previously running `latest-ipsw` VM has been stopped), and the recent `sonoma-latest` is now running. 
 
@@ -231,7 +229,7 @@
 
 ## Pulling Remote Images Locally
 
 In previous examples, `orka-engine vm run` was used to both _pull_ (or download) a remote image to the local device and to _run_ the vm. There are cases where users may just want to download an image, and `orka-engine image pull` supports this. 
 
 `orka-engine image pull ghcr.io/macstadium/orka-images/ventura:no-sip`
 
@@ -241,9 +239,9 @@
 
 ## Pushing local Images to Registry
 
 If the previously run sonoma-latest image has been modified and saved with the necessary CI tools, then it can image can be shared with team members by storing it on the team OCI repo and naming it **sequoiaCI** ; on the repo, use the `orka-engine image push` command. 
 
 The default local Orka Engine VM image files system path is `/Users/<host_username>/.local/share/orka/data/` where the host_username is **admin** in this example and the container registry is [ghcr.io](http://ghcr.io/) and the repo credentials are username=**dev1** and password=**repo**. 
 
 `orka-engine image push --username dev1 --password repo /Users/admin/.local/share/orka/data/sonoma-latest ghcr.io/images/sequoiaCI:latest `