From 12a853fab74de9d146580891d8b70a7c216d2c83 Mon Sep 17 00:00:00 2001
From: Vincent Ambo <tazjin@google.com>
Date: Mon, 5 Aug 2019 01:20:52 +0100
Subject: docs: Minor fixes to README after new website release

---
 tools/nixery/README.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

(limited to 'tools')

diff --git a/tools/nixery/README.md b/tools/nixery/README.md
index bcb8e40ec794..9c323a57fa12 100644
--- a/tools/nixery/README.md
+++ b/tools/nixery/README.md
@@ -1,5 +1,5 @@
 <div align="center">
-  <img src="static/nixery-logo.png">
+  <img src="docs/src/nixery-logo.png">
 </div>
 
 -----------------
@@ -16,12 +16,13 @@ image name.
 The path components refer to top-level keys in `nixpkgs` and are used to build a
 container image using Nix's [buildLayeredImage][] functionality.
 
+A public instance as well as additional documentation is available at
+[nixery.dev][public].
+
 The project started out with the intention of becoming a Kubernetes controller
 that can serve declarative image specifications specified in CRDs as container
 images. The design for this is outlined in [a public gist][gist].
 
-An example instance is available at [nixery.dev][demo].
-
 This is not an officially supported Google project.
 
 ## Usage example
@@ -94,7 +95,7 @@ variables:
 
 ## Roadmap
 
-### Kubernetes integration (in the future)
+### Kubernetes integration
 
 It should be trivial to deploy Nixery inside of a Kubernetes cluster with
 correct caching behaviour, addressing and so on.
@@ -104,5 +105,5 @@ See [issue #4](https://github.com/google/nixery/issues/4).
 [Nix]: https://nixos.org/
 [gist]: https://gist.github.com/tazjin/08f3d37073b3590aacac424303e6f745
 [buildLayeredImage]: https://grahamc.com/blog/nix-and-layered-docker-images
-[demo]: https://nixery.dev
+[public]: https://nixery.dev
 [gcs]: https://cloud.google.com/storage/
-- 
cgit 1.4.1