From f1c70b9acb8ed047d21ff47ae717d540824590b6 Mon Sep 17 00:00:00 2001
From: kwadronaut <kwadronaut@crackedwillow.net>
Date: Sun, 24 Oct 2010 19:45:48 +0200
Subject: typos

---
 index.mdwn | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/index.mdwn b/index.mdwn
index b5b4642..50bf41c 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -16,19 +16,19 @@ The core protocol is composed by the following metadata:
 * Layer name (if applicable).
 * Layer implementation (eg. if virtual zone: distro name, version, etc).
 * Available disk space.
-* Available memory,
+* Available memory.
 * Available CPU.
 * UPS capacity/characteristics.
 * Average downtime.
 * Timezone.
-* Available systen capabilities.
+* Available system capabilities.
 * Networking
   * Available bandwidth.
   * Real IP availability.
   * Proxy availability.
   * Firewall/routing availability.
   * VPN availability. 
-* Who admin/update the layer:
+* Who admins/updates the layer:
   * The hosting group?
   * The hosted group? 
 * Security:
@@ -45,7 +45,7 @@ The core protocol is composed by the following metadata:
     * Backup availability
       * No backups.
       * Local backups.
-      * Remote backups in more than a single place but in the same building/country/etc.
+      * Remote backups in more than a single place but in the same building/jurisdiction/etc.
       * Remote backups in more than a single place and also in other countries. 
     * Backup security
       * Have unencrypted backups.
@@ -70,7 +70,7 @@ The core protocol is composed by the following metadata:
 
 # Packages
 
-Even if the metadata supports different configurations, it can be unsuitable to use all set for each application or layer specificiation, especially if you're deadling with multiple layers, one atop of another. Then, it is possible to have a more generic list of prerequisite information, along the lines of a debian package. these are the debian headings:
+Even if the metadata supports different configurations, it can be unsuitable to use all set for each application or layer specificiation, especially if you're dealing with multiple layers, one atop of another. Then, it is possible to have a more generic list of prerequisite information, along the lines of a debian package. these are the debian headings:
 
       Package:
       State:
@@ -163,9 +163,9 @@ RSP development and maintenance ins't a hard task: it's just a matter of:
 * Try to fit all needs into the set.
 * KISS.
 
-# Analisys
+# Analysis
 
-See [[analisys]].
+See [[analysis|analisys]].
 
 # License
 
-- 
cgit v1.2.3