Update docs theme

akka-docs/java/agents.rst

@@ -4,10 +4,6 @@
  Agents (Java)
 ##############
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
-
 Agents in Akka are inspired by `agents in Clojure`_.
 
 .. _agents in Clojure: http://clojure.org/agents

akka-docs/java/dispatchers.rst

@@ -3,10 +3,6 @@
 Dispatchers (Java)
 ===================
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
-
 An Akka ``MessageDispatcher`` is what makes Akka Actors "tick", it is the engine of the machine so to speak.
 All ``MessageDispatcher`` implementations are also an ``ExecutionContext``, which means that they can be used
 to execute arbitrary code, for instance :ref:`futures-java`.

akka-docs/java/event-bus.rst

@@ -4,10 +4,6 @@
 Event Bus (Java)
 ################
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
-
 Originally conceived as a way to send messages to groups of actors, the
 :class:`EventBus` has been generalized into a set of composable traits
 implementing a simple interface:

akka-docs/java/extending-akka.rst

@@ -4,9 +4,6 @@
  Akka Extensions (Java)
 ########################
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
 
 If you want to add features to Akka, there is a very elegant, but powerful mechanism for doing so.
 It's called Akka Extensions and is comprised of 2 basic components: an ``Extension`` and an ``ExtensionId``.

akka-docs/java/fault-tolerance.rst

@@ -3,10 +3,6 @@
 Fault Tolerance (Java)
 ======================
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
-
 As explained in :ref:`actor-systems` each actor is the supervisor of its
 children, and as such each actor defines fault handling supervisor strategy.
 This strategy cannot be changed afterwards as it is an integral part of the

akka-docs/java/fsm.rst

@@ -4,9 +4,6 @@
 Building Finite State Machine Actors (Java)
 ###########################################
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
 
 Overview
 ========

akka-docs/java/futures.rst

@@ -3,10 +3,6 @@
 Futures (Java)
 ===============
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
-
 Introduction
 ------------
 

akka-docs/java/logging.rst

@@ -4,9 +4,6 @@
  Logging (Java)
 ################
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
 
 How to Log
 ==========

akka-docs/java/routing.rst

@@ -4,10 +4,6 @@
 Routing (Java)
 ==============
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
-
 A Router is an actor that routes incoming messages to outbound actors.
 The router routes the messages sent to it to its underlying actors called 'routees'.
 

akka-docs/java/serialization.rst

@@ -5,10 +5,6 @@
  Serialization (Java)
 #####################
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
-
 Akka has a built-in Extension for serialization,
 and it is both possible to use the built-in serializers and to write your own.
 

akka-docs/java/transactors.rst

@@ -4,10 +4,6 @@
  Transactors (Java)
 ####################
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
-
 
 Why Transactors?
 ================

akka-docs/java/typed-actors.rst

@@ -1,10 +1,6 @@
 Typed Actors (Java)
 ===================
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
-
 Akka Typed Actors is an implementation of the `Active Objects <http://en.wikipedia.org/wiki/Active_object>`_ pattern.
 Essentially turning method invocations into asynchronous dispatch instead of synchronous that has been the default way since Smalltalk came out.
 

akka-docs/java/untyped-actors.rst

@@ -6,11 +6,6 @@
 ################
 
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
-
-
 The `Actor Model`_ provides a higher level of abstraction for writing concurrent
 and distributed systems. It alleviates the developer from having to deal with
 explicit locking and thread management, making it easier to write correct

akka-docs/java/zeromq.rst

@@ -5,9 +5,6 @@
  ZeroMQ (Java)
 ###############
 
-.. sidebar:: Contents
-
-   .. contents:: :local:
 
 Akka provides a ZeroMQ module which abstracts a ZeroMQ connection and therefore allows interaction between Akka actors to take place over ZeroMQ connections. The messages can be of a proprietary format or they can be defined using Protobuf. The socket actor is fault-tolerant by default and when you use the newSocket method to create new sockets it will properly reinitialize the socket.