forked from toolshed/docs.coopcloud.tech
Fix broken links, tweak language
This commit is contained in:
@ -34,7 +34,7 @@ The project was started by workers at [Autonomic](https://autonomic.zone/) which
|
||||
|
||||
Please read our [initial project announcement post](https://autonomic.zone/blog/co-op-cloud/) for more on this.
|
||||
|
||||
Also see our [strategy page](/strategy/).
|
||||
Also see our [strategy page](../strategy/).
|
||||
|
||||
## How do I make a recipe for (package) an app?
|
||||
|
||||
@ -182,7 +182,7 @@ These are organisational concerns that Co-op Cloud can't solve for you which any
|
||||
|
||||
## What is important to consider when running containers in production?
|
||||
|
||||
The Co-op Cloud uses [containers](/faq/#why-containers) as a fundamental building block. Therefore it is important to be aware of some general principles for container management in production environments. These are typically things that you will want to discuss within your co-op or democratic collective about how to prioritise and build up process for.
|
||||
The Co-op Cloud uses [containers](#why-containers) as a fundamental building block. Therefore it is important to be aware of some general principles for container management in production environments. These are typically things that you will want to discuss within your co-op or democratic collective about how to prioritise and build up process for.
|
||||
|
||||
However, as the Co-op Cloud project is still very young, we're also still thinking about how we can make the platform itself mitigate problematic issues and make the maintenance of containers a more stable experience.
|
||||
|
||||
|
Reference in New Issue
Block a user