From 58b77ab4ae1239da08d43cb8bc316f6733512fea Mon Sep 17 00:00:00 2001 From: chri Date: Tue, 28 Aug 2012 10:45:53 +0200 Subject: Misc typos. --- docs/extensions/api.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/extensions') diff --git a/docs/extensions/api.txt b/docs/extensions/api.txt index 615c10c..69fb68e 100644 --- a/docs/extensions/api.txt +++ b/docs/extensions/api.txt @@ -103,7 +103,7 @@ that example pattern is not very DRY. A pattern for `**strong**` text would be almost identical, with the exception that it would create a 'strong' element. Therefore, Markdown provides a number of generic pattern classes that can provide some common functionality. For example, both emphasis and strong are -implemented with separate instances of the ``SimpleTagPettern`` listed below. +implemented with separate instances of the ``SimpleTagPattern`` listed below. Feel free to use or extend any of the Pattern classes found at `markdown.inlinepatterns`. **Generic Pattern Classes** @@ -358,7 +358,7 @@ Integrating Your Code Into Markdown {: #integrating_into_markdown } Once you have the various pieces of your extension built, you need to tell Markdown about them and ensure that they are run in the proper sequence. -Markdown accepts a ``Extension`` instance for each extension. Therefore, you +Markdown accepts an ``Extension`` instance for each extension. Therefore, you will need to define a class that extends ``markdown.extensions.Extension`` and over-rides the ``extendMarkdown`` method. Within this class you will manage configuration options for your extension and attach the various processors and -- cgit v1.2.3