[Commit-gnuradio] [gnuradio] 06/06: docs: fixed use of section tags in python_blocks docs.

[git]

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

trondeau pushed a commit to branch master
in repository gnuradio.

commit 885cc643b5a10c217f043caa2ac7f077d3a24bad
Author: Tom Rondeau <address@hidden>
Date:   Fri Jul 25 23:07:42 2014 -0400

    docs: fixed use of section tags in python_blocks docs.
---
 docs/doxygen/other/python_blocks.dox | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/doxygen/other/python_blocks.dox 
b/docs/doxygen/other/python_blocks.dox
index 811eb84..49273cd 100644
--- a/docs/doxygen/other/python_blocks.dox
+++ b/docs/doxygen/other/python_blocks.dox
@@ -2,7 +2,7 @@
 
 How to create blocks in Python
 
-\subsection pyblocks_streaming Streaming Data Blocks
+\section pyblocks_streaming Streaming Data Blocks
 
 We create blocks in Python very much like we would in C++, just with
 more Python. Figure out which type of block you want to create:
@@ -69,7 +69,7 @@ the size of the output_items vector.
 
 
 
-\subsection pyblocks_tags Using Stream Tags
+\section pyblocks_tags Using Stream Tags
 
 Python blocks have access to the stream tag system like their C++
 counterparts. The interface is almost identical except they behave
@@ -108,7 +108,7 @@ def work(self, input_items, output_items):
 
 
 
-\subsection pyblocks_msgs Using Message Passing
+\section pyblocks_msgs Using Message Passing
 
 Again, like their C++ counterparts, Python blocks can use the
 asynchronous message passing interface. We define output message