more documentation changes

Author: tschellenbach

docs/activity.rst

@@ -64,7 +64,7 @@ Just subclass the Verb class and give it a unique id.
     register(Pin)
         
 .. seealso:: Make sure your verbs are registered before you read data from feedly, if you use django
-you can just define/import them in models.py to make sure they are loaded early
+	you can just define/import them in models.py to make sure they are loaded early
 
 
 Activity serialization

docs/background_tasks.rst

@@ -35,20 +35,16 @@ to scale up capacity less often.
 Feedly manager is the best place to implement your high/low priority fanouts, in fact the `get_follower_ids` method
 is required to return the feed ids grouped by priority.
 
-eg.
-
-```python
-
-class MyFeedlyManager(Feedly):
-
-    def get_user_follower_ids(self, user_id):
-    	follower_ids = {
-        	FanoutPriority.HIGH: get_follower_ids(user_id, active=True),
-        	FanoutPriority.LOW: get_follower_ids(user_id, active=False)
-        }
-        return follower_ids
-
-```
+eg::
+
+	class MyFeedlyManager(Feedly):
+	
+	    def get_user_follower_ids(self, user_id):
+	    	follower_ids = {
+	        	FanoutPriority.HIGH: get_follower_ids(user_id, active=True),
+	        	FanoutPriority.LOW: get_follower_ids(user_id, active=False)
+	        }
+	        return follower_ids
 
 
 Celery and Django

docs/choosing_a_storage_backend.rst

@@ -14,7 +14,7 @@ to store all the data in Redis. For larger use cases we therefor recommend Cassa
 
 
 Redis (2.7 or newer)
-******
+********************
 
 PROS:
 
@@ -48,7 +48,7 @@ In conclusion I believe Redis is your best bet if you can fallback to
 the database when needed.
 
 Cassandra (2.0 or newer)
-******
+************************
 
 PROS:
 

docs/feedly.feeds.aggregated_feed.rst

@@ -33,7 +33,7 @@ aggregated_feed Package
     :undoc-members:
     :show-inheritance:
 
-:mod:`notificatoin_feed` Module
+:mod:`notification_feed` Module
 -------------------
 
 .. automodule:: feedly.feeds.aggregated_feed.notification_feed

docs/feedly.rst

@@ -34,14 +34,6 @@ feedly Package
     :undoc-members:
     :show-inheritance:
 
-:mod:`marker` Module
---------------------
-
-.. automodule:: feedly.marker
-    :members:
-    :undoc-members:
-    :show-inheritance:
-
 :mod:`settings` Module
 ----------------------
 

feedly/feed_managers/base.py

@@ -49,7 +49,6 @@ class Feedly(object):
     to all their follower's feeds
 
     .. note::
-
         Fanout is the process which pushes a little bit of data to all of your
         followers in many small and asynchronous tasks.
 
@@ -60,7 +59,7 @@ class Feedly(object):
     - user_feed_class
 
     **Example** ::
-
+    
         from feedly.feed_managers.base import Feedly
 
         class PinFeedly(Feedly):
@@ -327,7 +326,7 @@ def fanout(self, user_ids, feed_class, operation, operation_kwargs):
         This functionality is called from within feedly.tasks.fanout_operation
 
         :param user_ids: the list of user ids which feeds we should apply the
-        operation against
+            operation against
         :param feed_class: the feed to run the operation on
         :param operation: the operation to run on the feed
         :param operation_kwargs: kwargs to pass to the operation

feedly/feeds/base.py

@@ -10,7 +10,6 @@
 
 
 class BaseFeed(object):
-
     '''
     The feed class allows you to add and remove activities from a feed.
     Please find below a quick usage example.
@@ -47,7 +46,7 @@ class MyFeed(BaseFeed):
         feed.filter(activity_id__lt=1)[:10]
 
 
-    **Activity storage and Timeline storage**::
+    **Activity storage and Timeline storage**
 
     To keep reduce timelines memory utilization the BaseFeed supports
     normalization of activity data.