remove redundant pages

Author: gilesknap

docs/explanations/introduction.md

@@ -230,7 +230,6 @@ line entry point is **ec**.
 
 The project is a python package featuring simple command line functions for deploying and monitoring IOC instances. It is a thin wrapper around the ArgoCD, kubectl, helm and git commands. This tool can be used by developers and beamline staff to get a quick CLI based view of IOCs running in the cluster, as well as stop/start and obtain logs from them.
 
-See {any}`CLI` for more details.
 
 ### **ibek**
 

docs/genindex.md

@@ -6,4 +6,4 @@ epics-containers supports auto generation of engineering screens for Phoebus usi
 
 Auto-generation of engineering screens is now supported in generic IOCs.
 
-See here for an example https://github.com/epics-containers/example-services.
+See here for an example [example-services](https://github.com/epics-containers/example-services).

docs/how-to/phoebus.md

@@ -7,6 +7,5 @@ Technical reference material including APIs and release notes.
 :glob:
 
 reference/*
-genindex
 Release Notes <https://github.com/epics-containers/epics-containers.github.io/releases>
 ```

docs/how-to/update_generic_ioc.md

@@ -2,11 +2,6 @@
 
 (no-opi)=
 
-## Why no mention of Operator Interfaces?
-
-UPDATE: with the introduction of PVI we are providing auto generated
-engineering screens. TODO: more details will be added to a new section.
-
 ## Why have ioc-XXX repositories?
 
 Why not put the Dockerfile and image generating in the support module itself

docs/how-to/useful_k8s.md

@@ -16,7 +16,6 @@ epics-containers supports two kinds of services repositories:
 
 A Python command line tool for the developer that runs *outside* of containers. It provides simple features for and monitoring and managing and IOC instances within a [](services-repo).
 
-So named 'edge' containers because these services all run close to the hardware. Uses the command line entry point `ec`. See {std:ref}`cli` for more details.
 
 (ibek)=
 ## ibek