Fixing incorrect inter-linking

basics.asciidoc

@@ -443,7 +443,7 @@ print i
 Sometimes, there is an implicit assumption where you don't need to use a backslash. This is the
 case where the logical line has a starting parentheses, starting square brackets or a starting
 curly braces but not an ending one. This is called *implicit line joining*. You can see this in
-action when we write programs using <<lists,lists>> in later chapters.
+action when we write programs using <<list,lists>> in later chapters.
 
 [[indentation]]
 === Indentation

functions.asciidoc

@@ -325,7 +325,7 @@ include::programs/function_docstring.txt[]
 .How It Works
 
 A string on the first logical line of a function is the *docstring* for that function. Note that
-DocStrings also apply to <<modules,modules>> and <<oop,classes>> which we will learn about in the
+DocStrings also apply to <<module,modules>> and <<oop,classes>> which we will learn about in the
 respective chapters.
 
 The convention followed for a docstring is a multi-line string where the first line starts with a

modules.asciidoc

@@ -1,4 +1,4 @@
-[[modules]]
+[[module]]
 == Modules
 
 You have seen how you can reuse code in your program by defining functions once. What if you wanted
@@ -302,7 +302,7 @@ This is how you would structure the folders:
 --------------------------------------------------
 
 Packages are just a convenience to hierarchically organize modules. You will see many instances of
-this in the <<standard_library,standard library>>.
+this in the <<stdlib,standard library>>.
 
 === Summary
 

more.asciidoc

@@ -213,7 +213,7 @@ See:
 -  http://www.ibm.com/developerworks/linux/library/l-cpdecor.html
 - http://toumorokoshi.github.io/dry-principles-through-python-decorators.html
 
-[[2_vs_3]]
+[[two_vs_three]]
 === Differences between Python 2 and Python 3
 
 See: