reorder pages

content/modules/ROOT/nav.adoc

@@ -1,6 +1,6 @@
 * xref:01-overview.adoc[Environment Overview]
 * xref:02-vllm.adoc[vLLM]
-* xref:03-elasticsearch.adoc[Elasticsearch]
-* xref:040-assistant.adoc[Assistant]
-* xref:041-rag-assistant.adoc[Retrieval-Augmented Generation (RAG)]
-* xref:05-diy.adoc[(Optional) Find your own doc]
+* xref:03-assistant.adoc[Assistant]
+* xref:04-elasticsearch.adoc[Elasticsearch]
+* xref:05-rag-assistant.adoc[Retrieval-Augmented Generation (RAG)]
+* xref:06-diy.adoc[(Optional) Find your own doc]

content/modules/ROOT/pages/040-assistant.adoc → content/modules/ROOT/pages/03-assistant.adoc

@@ -8,7 +8,7 @@ Assistants are a core concept in how Composer AI works, and the main way in whic
 
 An `Assistant` is an object stored in our database and contains a Prompt and the flow that Composer will use to orchestrate the response to a message from the user.
 
-image::040-Composer_Assistants.drawio.png[Assistant Graph]
+image::03-composer-assistants.drawio.png[Assistant Graph]
 
 NOTE: Currently Composer only supports simple RAG flows but we have future plans to expand into more complex flows. 
 
@@ -37,7 +37,7 @@ Prompt: Respond to the user in Pig Latin
 
 +
 [.bordershadow]
-image::040-Create-Basic-Assistant.png[Create Basic Assistant]
+image::03-create-basic-assistant.png[Create Basic Assistant]
 
 === Testing Basic Assistant
 

content/modules/ROOT/pages/03-elasticsearch.adoc → content/modules/ROOT/pages/04-elasticsearch.adoc

@@ -11,17 +11,17 @@ The Elasticsearch (ECK) Operator has already been installed on the cluster for y
 . With the `composer-ai-apps` namespace selected in the OpenShift Web Console, navigate to `Operators` > `Installed Operators` and select the `Elasticsearch (ECK) Operator`.
 
 +
-image::03-elasticsearch-operator.png[Elasticsearch Operator]
+image::04-elasticsearch-operator.png[Elasticsearch Operator]
 
 . Click the `+Create instance` option for an `Elasticsearch Cluster`
 
 +
-image::03-elasticsearch-operator.png[Elasticsearch Operator]
+image::04-elasticsearch-operator.png[Elasticsearch Operator]
 
 . Update the object name to `elasticsearch` and click `Create`.
 
 +
-image::03-elasticsearch-yaml.png[Elasticsearch YAML]
+image::04-elasticsearch-yaml.png[Elasticsearch YAML]
 
 Three new Elasticsearch pods will be created in the `composer-ai-apps` namespace.  Once they are Ready, you are ready to move on to the next step.
 
@@ -38,12 +38,12 @@ For demonstration purposes we will be ingesting documentation for various Red Ha
 
 To get you started, we have included an ingestion pipeline to populate the elasticsearch instance with information pulled from openshift documentation.  Go to pipelines in the composer-ai-apps namespaces.  Run the `ingestion-pipeline` pipeline with the default parameters.  Set the `source` workspace to the VolumeClaimTemplate option.  
 
-image::03-show-pipeline-1.png[Instantiate Template]
+image::04-show-pipeline-1.png[Instantiate Template]
 
-image::03-show-pipeline-2.png[Instantiate Template]
+image::04-show-pipeline-2.png[Instantiate Template]
 
 The progress can be viewed in the "Experiments and runs" section in the Openshift AI console.
 
-image::03-view-experiments.png[Instantiate Template]
+image::04-view-experiments.png[Instantiate Template]
 
 From here you can view the progress of the Kubeflow Pipeline (KFP), as well as the logs of individual steps, similar to Tekton.