[Pkg-privacy-commits] [onionbalance] 75/117: Change readme headings, make list items consistant [ci skip]

[Donncha O'Cearbahill]

This is an automated email from the git hooks/post-receive script.

donncha-guest pushed a commit to branch debian/sid
in repository onionbalance.

commit 90f41d06c8d637e42317d281f8a8a35f494278bf
Author: Donncha O'Cearbhaill <donncha at donncha.is>
Date:   Tue Jun 30 14:31:28 2015 +0100

    Change readme headings, make list items consistant [ci skip]
---
 README.rst     | 11 +++++++----
 docs/index.rst |  6 +-----
 2 files changed, 8 insertions(+), 9 deletions(-)

diff --git a/README.rst b/README.rst
index 9136f62..7c732c0 100644
--- a/README.rst
+++ b/README.rst
@@ -1,3 +1,6 @@
+OnionBalance
+============
+
 Introduction
 ------------
 
@@ -96,19 +99,19 @@ Multiple OnionBalance management servers can be run to make your service more re
 Use Cases
 ---------
 
-- A popular onion service with an overloaded web server or Tor process:
+- A popular onion service with an overloaded web server or Tor process
 
   A service such as Facebook which gets a large number of users would like to distribute client requests across multiple servers as the load is too much for a single Tor instance to handle. They would also like to balance between instances when the 'encrypted services' proposal is implemented [2555].
 
-- Redundancy and automatic failover:
+- Redundancy and automatic failover
 
   A political activist would like to keep their web service accessible and secure in the event that the secret police seize some of their servers. Clients should ideally automatically fail-over to another online instances with minimal service disruption.
 
-- 'Shared Hosting' scenarios:
+- 'Shared Hosting' scenarios
 
   A hosting provider wishes to allow their customers to access their shared hosting control panel over an encrypted onion service. Rather than creating an individual onion service (with corresponding overhead) for thousands of customers, the host could instead run one onion service. Multiple service descriptors could then be published under unique customer onion addresses which would then be routed to that users control panel. This could also enable a low-resourced OnionFlare-type implem [...]
 
-- Secure Onion Service Key storage:
+- Secure Onion Service Key storage
 
   An onion service operator would like to compartmentalize their permanent onion key in a secure location separate to their Tor process and other services. With this proposal permanent keys could be stored on an independent, isolated system.
 
diff --git a/docs/index.rst b/docs/index.rst
index 3e1fad3..239d974 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -3,12 +3,8 @@
    You can adapt this file completely to your liking, but it should at least
    contain the root `toctree` directive.
 
-Welcome to OnionBalance's documentation!
-========================================
-
 .. include:: ../README.rst
 
-
 ----
 
 
@@ -16,7 +12,7 @@ Contents
 ========
 
 .. toctree::
-   :maxdepth: 3
+   :maxdepth: 2
 
    onionbalance
    design

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-privacy/packages/onionbalance.git