Stabilize logically bound images

The feature is working as is and provides a lot of value, so let's stabilize it.

Signed-off-by: Colin Walters <[email protected]>

docs/src/SUMMARY.md

@@ -19,6 +19,7 @@
 
 - [Upgrade and rollback](upgrades.md)
 - [Accessing registries and offline updates](registries-and-offline.md)
+- [Logically bound images](logically-bound-images.md)
 - [Booting local builds](booting-local-builds.md)
 - [`man bootc`](man/bootc.md)
 - [`man bootc-status`](man/bootc-status.md)
@@ -48,7 +49,6 @@
 # Experimental features
 
 - [bootc image](experimental-bootc-image.md)
-- [logically bound images](experimental-logically-bound-images.md)
 
 # More information
 

docs/src/experimental-logically-bound-images.md → docs/src/logically-bound-images.md

@@ -1,13 +1,8 @@
 # Logically Bound Images
 
-Experimental features are subject to change or removal. Please
-do provide feedback on them.
-
-Tracking issue: <https://github.com/containers/bootc/issues/128>
-
 ## About logically bound images
 
-This experimental feature enables an association of container "app" images to a base bootc system image. Use cases for this include:
+This feature enables an association of container "app" images to a base bootc system image. Use cases for this include:
 
 - Logging (e.g. journald->remote log forwarder container)
 - Monitoring (e.g. [Prometheus node_exporter](https://github.com/prometheus/node_exporter))