From f2f66988ac972768300ff783b60e29b1f7c4292e Mon Sep 17 00:00:00 2001 From: Ryan Cook Date: Thu, 11 Nov 2021 14:09:35 -0500 Subject: [PATCH] link fix --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 42f38e8893..e9af7fdf54 100644 --- a/README.md +++ b/README.md @@ -76,14 +76,14 @@ rm -rf /var/lib/microshift && rm -r $HOME/.microshift In production environment MicroShift can be deployed as: -1. Install via an RPM, utilizing a host-provided cri-o runtime and be lifecycle-managed by systemd -2. [Install as a container via Podman, utilizing cri-o runtime and be lifecycle-managed by systemd](https://microshift.io/docs/deployment-modes/microshift-containerized/) +1. [Install via an RPM, utilizing a host-provided cri-o runtime and be lifecycle-managed by systemd](https://microshift.io/docs/developer-documentation/build-install-rpm/) +2. [Install as a container via Podman, utilizing cri-o runtime and be lifecycle-managed by systemd](https://microshift.io/docs/user-documentation/deploying-microshift/containerized/) For app developer deployments: -1. [Run an all-in-one microshift deployment on which devs can test their applications locally](https://microshift.io/docs/deployment-modes/microshift-aio/). `microshift-aio` packages cri-o runtime and can be run and managed via podman and systemd +1. [Run an all-in-one microshift deployment on which devs can test their applications locally](https://microshift.io/docs/getting-started/experimental-development/). `microshift-aio` packages cri-o runtime and can be run and managed via podman and systemd -## [Known Issues](https://microshift.io/docs/known-issues/known-issues/) +## [Known Issues](https://microshift.io/docs/user-documentation/troubleshooting/) ## Developing MicroShift