Small additions

Include the concept of a composable OS and a link to sigstore.

Signed-off-by: Josh Boyer <[email protected]>

index.md

@@ -6,15 +6,15 @@ layout: home
 ## Image Based Linux with Bootable Container Images
 
 Over the last decade, [OCI containers](https://specs.opencontainers.org/image-spec/) have become a de facto way to deploy a complete functioning Linux user space as an application.
-A large set of practices and tooling has evolved around them.
+A large set of practices and tooling have evolved around them.
 Bootable containers are a modern opinionated way of deploying, configuring and managing immutable image based Linux systems.
 
 Our goals are:
 
-1. Use standard container practices and tooling, such as the [OCI standard](https://specs.opencontainers.org/image-spec/), layering, container registries, signing, testing, and GitOps workflows to build Linux systems.
+1. Use standard container practices and tooling, such as the [OCI standard](https://specs.opencontainers.org/image-spec/), layering, container registries, [signing](https://docs.sigstore.dev/signing/signing_with_containers/), testing, and GitOps workflows to build Linux systems.
 
 1. Container images describe the operating system behavior as a prebuilt predefined unit, rather than defined during deployment out of fine grained packages.
-There is a strong bias toward having the full system definition committed to version control, including a list of components, application files and system configuration.
+There is a strong bias toward having the full system definition committed to version control, including a list of components, application files and system configuration.  This bias helps implement the concept of a more composable operating system.
 
 1. The system updates atomically.
 It is robust to power outages or software failures during updates.