Skip to content
This repository
Browse code

Fixed: Typo errors in readme file.

  • Loading branch information...
commit c89732d5cc2c5af1ac4394c255e77b0be87fb395 1 parent b1bc42e
authored February 29, 2012

Showing 1 changed file with 21 additions and 21 deletions. Show diff stats Hide diff stats

  1. 42  PHP Markdown Readme.text
42  PHP Markdown Readme.text
@@ -23,8 +23,8 @@ PHP Markdown is a port to PHP of the original Markdown program by
23 23
 John Gruber.
24 24
 
25 25
 PHP Markdown can work as a plug-in for WordPress and bBlog, as a 
26  
-modifier for the Smarty templating engine, or as a remplacement for
27  
-textile formatting in any software that support textile.
  26
+modifier for the Smarty templating engine, or as a replacement for
  27
+Textile formatting in any software that supports Textile.
28 28
 
29 29
 Full documentation of Markdown's syntax is available on John's 
30 30
 Markdown page: <http://daringfireball.net/projects/markdown/>
@@ -42,7 +42,7 @@ PHP Markdown works with [WordPress][wp], version 1.2 or later.
42 42
 
43 43
  [wp]: http://wordpress.org/
44 44
 
45  
-1.  To use PHP Markdown with WordPress, place the "makrdown.php" file 
  45
+1.  To use PHP Markdown with WordPress, place the "markdown.php" file 
46 46
     in the "plugins" folder. This folder is located inside 
47 47
     "wp-content" at the root of your site:
48 48
 
@@ -51,17 +51,17 @@ PHP Markdown works with [WordPress][wp], version 1.2 or later.
51 51
 2.  Activate the plugin with the administrative interface of 
52 52
     WordPress. In the "Plugins" section you will now find Markdown. 
53 53
     To activate the plugin, click on the "Activate" button on the 
54  
-    same line than Markdown. Your entries will now be formatted by 
  54
+    same line as Markdown. Your entries will now be formatted by 
55 55
     PHP Markdown.
56 56
 
57 57
 3.  To post Markdown content, you'll first have to disable the 
58  
-	"visual" editor in the User section of WordPress.
  58
+    "visual" editor in the User section of WordPress.
59 59
 
60 60
 You can configure PHP Markdown to not apply to the comments on your 
61 61
 WordPress weblog. See the "Configuration" section below.
62 62
 
63 63
 It is not possible at this time to apply a different set of 
64  
-filters to different entries. All your entries will be formated by 
  64
+filters to different entries. All your entries will be formatted by 
65 65
 PHP Markdown. This is a limitation of WordPress. If your old entries 
66 66
 are written in HTML (as opposed to another formatting syntax, like 
67 67
 Textile), they'll probably stay fine after installing Markdown.
@@ -88,19 +88,19 @@ entry. This setting will only apply to the entry you are editing.
88 88
 
89 89
 [TextPattern][tp] use [Textile][tx] to format your text. You can 
90 90
 replace Textile by Markdown in TextPattern without having to change
91  
-any code by using the *Texitle Compatibility Mode*. This may work 
  91
+any code by using the *Textile Compatibility Mode*. This may work 
92 92
 with other software that expect Textile too.
93 93
 
94 94
  [tx]: http://www.textism.com/tools/textile/
95 95
  [tp]: http://www.textpattern.com/
96 96
 
97 97
 1.  Rename the "markdown.php" file to "classTextile.php". This will
98  
-	make PHP Markdown behave as if it was the actual Textile parser.
  98
+    make PHP Markdown behave as if it was the actual Textile parser.
99 99
 
100 100
 2.  Replace the "classTextile.php" file TextPattern installed in your
101  
-	web directory. It can be found in the "lib" directory:
  101
+    web directory. It can be found in the "lib" directory:
102 102
 
103  
-		(site home)/textpattern/lib/
  103
+        (site home)/textpattern/lib/
104 104
 
105 105
 Contrary to Textile, Markdown does not convert quotes to curly ones 
106 106
 and does not convert multiple hyphens (`--` and `---`) into en- and 
@@ -211,11 +211,11 @@ Version History
211 211
 
212 212
 *	Enabled reference-style shortcut links. Now you can write reference-style 
213 213
 	links with less brakets:
214  
-	
  214
+
215 215
 		This is [my website].
216  
-		
  216
+
217 217
 		[my website]: http://example.com/
218  
-	
  218
+
219 219
 	This was added in the 1.0.2 betas, but commented out in the 1.0.1 branch, 
220 220
 	waiting for the feature to be officialized. [But half of the other Markdown
221 221
 	implementations are supporting this syntax][half], so it makes sense for 
@@ -225,7 +225,7 @@ Version History
225 225
 
226 226
 *	Now accepting many valid email addresses in autolinks that were 
227 227
 	previously rejected, such as:
228  
-	
  228
+
229 229
 		<abc+mailbox/department=shipping@example.com>
230 230
 		<!#$%&'*+-/=?^_`.{|}~@example.com>
231 231
 		<"abc@def"@example.com>
@@ -234,7 +234,7 @@ Version History
234 234
 
235 235
 *	Now accepting spaces in URLs for inline and reference-style links. Such 
236 236
 	URLs need to be surrounded by angle brakets. For instance:
237  
-	
  237
+
238 238
 		[link text](<http://url/with space> "optional title")
239 239
 
240 240
 		[link text][ref]
@@ -278,27 +278,27 @@ Version History
278 278
 
279 279
 *	Fix for code blocks as first element of a list item. Previously,
280 280
 	this didn't create any code block for item 2:
281  
-	
  281
+
282 282
 		*   Item 1 (regular paragraph)
283  
-		
  283
+
284 284
 		*       Item 2 (code block)
285 285
 
286 286
 *	A code block starting on the second line of a document wasn't seen
287 287
 	as a code block. This has been fixed.
288  
-	
  288
+
289 289
 *	Added programatically-settable parser properties `predef_urls` and 
290 290
 	`predef_titles` for predefined URLs and titles for reference-style 
291 291
 	links. To use this, your PHP code must call the parser this way:
292  
-	
  292
+
293 293
 		$parser = new Markdwon_Parser;
294 294
 		$parser->predef_urls = array('linkref' => 'http://example.com');
295 295
 		$html = $parser->transform($text);
296  
-	
  296
+
297 297
 	You can then use the URL as a normal link reference:
298 298
 	
299 299
 		[my link][linkref]	
300 300
 		[my link][linkRef]
301  
-		
  301
+
302 302
 	Reference names in the parser properties *must* be lowercase.
303 303
 	Reference names in the Markdown source may have any case.
304 304
 

0 notes on commit c89732d

Please sign in to comment.
Something went wrong with that request. Please try again.