From 47978fcfc9362f659c1406fa60f1de7d21d1e50e Mon Sep 17 00:00:00 2001
From: notgne2
Date: Tue, 10 Nov 2020 23:16:17 -0700
Subject: Re-order link to examples in overall usage section in README

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'README.md')

diff --git a/README.md b/README.md
index c6d7d62..e24a175 100644
--- a/README.md
+++ b/README.md
@@ -33,6 +33,8 @@ There is also an `activate` binary though this should be ignored, it is only use
 
 `deploy-rs` also outputs a `lib` attribute, with tools used to make your definitions simpler and safer, including `deploy-rs.lib.${system}.setActivate` (see later section "Profile"), and `deploy-rs.lib.${system}.deployChecks` which will let `nix flake check` ensure your deployment is defined correctly.
 
+There are full working deploy-rs Nix expressions in the [examples folder](./examples), and there is a JSON schema [here](./interface.json) which is used internally by the `deployChecks` mentioned above to validate your expressions.
+
 A basic example of a flake that works with `deploy-rs` and deploys a simple NixOS configuration could look like this
 
 ```nix
@@ -59,8 +61,6 @@ A basic example of a flake that works with `deploy-rs` and deploys a simple NixO
 }
 ```
 
-There are full working deploy-rs Nix expressions in the [examples folder](./examples), and there is a JSON schema [here](./interface.json) which is used internally by the `deployChecks` mentioned above to validate your expressions.
-
 ### Profile
 
 This is the core of how `deploy-rs` was designed, any number of these can run on a node, as any user (see further down for specifying user information). If you want to mimick the behaviour of traditional tools like NixOps or Morph, try just defining one `profile` called `system`, as root, containing a nixosSystem, and you can even similarly use [home-manager](https://github.com/nix-community/home-manager) on any non-privileged user.
-- 
cgit v1.2.3