Fixing broken links

documentation/src/content/_index.md

@@ -19,18 +19,18 @@ The following key topics will be touched to showcase la1r:
 * And many more things!
 
 {{< columns >}}
-## Conceptual documentation
-This documentation captures the underlying concepts, goals and roadmap for the La1r project.
+## Capability Architecture
+This documentation captures the underlying capabilities, concepts, goals and roadmap for the La1r project from a functional perspective.
 
-[Read more](/docs/conceptual-setup)
+[Read more](/docs/capability-architecture)
 
 <--->
 
 
-## Technical documentation
+## Technical Architecture
 All the details on how each of the concepts is implemented can be found here. It will also contain details on the roadmap based on the conceptual roadmap.
 
-[Read more](/docs/technical-setup)
+[Read more](/docs/technical-architecture)
 
 {{< /columns >}}
 
@@ -41,7 +41,7 @@ I created a planning to ensure la1r isn't a fully unguided experiment, but it is
 
 ## Why this site?
 I noticed that combining all of these applications into a single integration environment can be challenging to keep all documentation and notes into a single place. To force myself to properly document my steps and also to give back to the open-source community, I decided to publish all of it on this domain. Hopefully it can also help others with similar aspirations.
-Feel free to share this site with other enthausiasts.
+Feel free to share this site with other enthusiasts.
 
 ### "Please **do** try this at home"
 Since this overview is focussed on sharing, I would like to invite anyone to try everything at home, it will not have insane hardware requirements or require niche hardware setups.

documentation/src/content/docs/capability-architecture/_index.md

@@ -31,7 +31,7 @@ To summarize, we identify several conceptual components:
 
 ## Conceptual Architecture Principles
 The la1r architecture followes several conceptual principles which components in its architecture should follow.
-Since this will not capture implementation specific / technical principles, a section on technical principles is describe [in the technical architecture page](./technical-setup)
+Since this will not capture implementation specific / technical principles, a section on technical principles is describe [in the technical architecture page](./technical-architecture)
 
 1. Data is realtime and streaming - Always assume that data, streaming through the la1r infrastructure is in streaming "format". Do not unnecessarily store it, or batch it when realtime streaming solutions can also be applied
 1. Don't assume information share - since an enterprise environment is conceptually simulated, it should also be simulated that (conceptual) teams are not fully aware of all integrations made by other (conceptual) teams. The implications of this is that there is a need for decoupling and formal information definitions. An example of this is the site you're currently reading, but further efforts should be made such as formal separation of layers, environments and data to appropriately conform to this conceptual requirement. 
@@ -43,14 +43,14 @@ Since there needs to be a way of formally converging to an aligned data setup, a
 This event specification will dictate how all events in the structured stream should be shaped.
 Events not conforming to this standard can be disregarded.
 
-[Read more](/docs/conceptual-setup/event-specifications)
+[Read more](/docs/capability-architecture/event-specifications)
 
 <--->
 
 ## Governance Catalogs
 Since we are still "simulating" an enterprise environment, and since my own memory is sub-optimal, appropriate governance catalogs need to be setup to fully capture the IT landscape on several domains.
 
-[Read more](/docs/conceptual-setup/governance-catalogs)
+[Read more](/docs/capability-architecture/governance-catalogs)
 
 <--->
 

documentation/src/content/docs/technical-architecture/_index.md

@@ -44,7 +44,7 @@ Setup of several security concepts which are an integral part of the technical a
 
 ## Technical Architecture principles
 The la1r architecture follows several technical principles which components in its architecture should follow.
-Since this will not capture conceptual principles, a section on conceptual principles is describe [in the capability architecture page](./conceptual-setup)
+Since this will not capture conceptual principles, a section on conceptual principles is describe [in the capability architecture page](./capability-architecture)
 
 1. Only the paranoid survive, apply and practice backup scenarios. - Backup scenarios should not only be implemented as tick in the box for our list of non functional requirements (nfrs), but should also be practiced where possible.
 1. Aim for near horizontal scaling - all services should be able to scale with cluster size. The infrastructure architecture of my current implementation is rather rigid, but the applications on it should be aimed on flexible and horizontally scalable underlying infrastructure.

documentation/src/content/docs/technical-architecture/application-architecture/_index.md

@@ -1,7 +1,7 @@
 ---
 title: Application Architecture
 type: docs
-bookToc: true
+bookToc: false
 bookCollapseSection : false
 weight: 4
 ---

documentation/src/content/docs/technical-architecture/data-architecture/_index.md

@@ -13,7 +13,7 @@ They all focus on contribution enhanced "intelligent" decision making in the La1
 Since there can be a large difference between how data is received, for example for commercial of the shelf (COTS) applications, and how it should be structured conforming to the described event standard, there is a need for (streaming) Transformations.
 
 #### Streaming analytics as default
-Since La1r is applying a Kappa architecture (see [capability architecture](./conceptual-setup) for more details on this), it is essential that as many of it's processes occur in a streaming fashion.
+Since La1r is applying a Kappa architecture (see [capability architecture](./capability-architecture) for more details on this), it is essential that as many of it's processes occur in a streaming fashion.
 This also includes all the performed analytics.
 Streaming analytics brings new considerations, such as messaging ordering and quality of prefix data.
 Since these concepts are handled out-of-the-box (OOTB) in Spark 2.x, Spark 2.x is considered as the default method of applying streaming analytics.