From 98a6febb5033406f58571099adf3df1a2323efa0 Mon Sep 17 00:00:00 2001
From: Takafumi Arakaki <aka.tkf@gmail.com>
Date: Fri, 15 Feb 2013 18:31:05 +0100
Subject: [PATCH] Fix typo s/Epidoc/Epydoc/g and add links for markups

---
 jedi/docstrings.py | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/jedi/docstrings.py b/jedi/docstrings.py
index 8f11e906..bbc5290b 100644
--- a/jedi/docstrings.py
+++ b/jedi/docstrings.py
@@ -4,8 +4,8 @@ Docstrings are another source of information for functions and classes.
 parsing is much easier. There are two different types of docstrings that |jedi|
 understands:
 
-- Sphinx
-- Epidoc
+- `Sphinx <http://sphinx-doc.org/markup/desc.html#info-field-lists>`_
+- `Epydoc <http://epydoc.sourceforge.net/manual-fields.html>`_
 
 For example, the sphinx annotation ``:type foo: str`` clearly states that the
 type of ``foo`` is ``str``.
@@ -23,12 +23,12 @@ import parsing
 
 DOCSTRING_PARAM_PATTERNS = [
     r'\s*:type\s+%s:\s*([^\n]+)',  # Sphinx
-    r'\s*@type\s+%s:\s*([^\n]+)',  # Epidoc
+    r'\s*@type\s+%s:\s*([^\n]+)',  # Epydoc
 ]
 
 DOCSTRING_RETURN_PATTERNS = [
         re.compile(r'\s*:rtype:\s*([^\n]+)', re.M),  # Sphinx
-        re.compile(r'\s*@rtype:\s*([^\n]+)', re.M),  # Epidoc
+        re.compile(r'\s*@rtype:\s*([^\n]+)', re.M),  # Epydoc
 ]
 
 REST_ROLE_PATTERN = re.compile(r':[^`]+:`([^`]+)`')