Permalink
Browse files

Fix typos in readme.md.

  • Loading branch information...
1 parent 5231b3c commit df4b51f50a1eafe92cbd3e2831b5c4e9fbd78a22 @jayarjo jayarjo committed Feb 14, 2013
Showing with 3 additions and 3 deletions.
  1. +3 −3 readme.md
View
@@ -22,7 +22,7 @@ Historically Plupload comes from dark and hostile age of no HTML5, hence all the
Plupload has started in times, when uploading a file in responsive and customizable manner was real pain. Internally browsers had only `input[type="file"]` element, that was ugly and clunky at the same time. One couldn't even change it's visuals, without hiding it and coding another one on top of it from scratch. And then there was no progress indication for upload process... Sounds pretty crazy today.
-It was very logical that developers started to look for alternatives and writing their own implementations, using Flash and Java, in order to somehow extend limited browser capabilities. And so did, in a search for reliable and flexible file uploader for our [TinyMCE](http://www.tinymce.com/index.php)'s [MCImageManager](http://www.tinymce.com/enterprise/mcimagemanager.php). Quickly enough though, Plupload grew up so big, that easily split into a standalone project. With major *version 2.0* it underwent another huge reconstruction, basically [from the ground up](http://blog.moxiecode.com/2012/11/28/first-public-beta-plupload-2/), as all the low-level runtime logic has been extracted into separate [File API](http://www.w3.org/TR/FileAPI/) and [XHR L2](http://www.w3.org/TR/XMLHttpRequest/) pollyfills (currently known under combined name of [mOxie](https://github.com/moxiecode/moxie)), giving Plupload a chance to evolve further.
+It was very logical that developers started to look for alternatives and writing their own implementations, using Flash and Java, in order to somehow extend limited browser capabilities. And so did we, in a search for reliable and flexible file uploader for our [TinyMCE](http://www.tinymce.com/index.php)'s [MCImageManager](http://www.tinymce.com/enterprise/mcimagemanager.php). Quickly enough though, Plupload grew up so big, that easily split into a standalone project. With major *version 2.0* it underwent another huge reconstruction, basically [from the ground up](http://blog.moxiecode.com/2012/11/28/first-public-beta-plupload-2/), as all the low-level runtime logic has been extracted into separate [File API](http://www.w3.org/TR/FileAPI/) and [XHR L2](http://www.w3.org/TR/XMLHttpRequest/) pollyfills (currently known under combined name of [mOxie](https://github.com/moxiecode/moxie)), giving Plupload a chance to evolve further.
<a name="structure" />
### Structure
@@ -37,9 +37,9 @@ Currently Plupload may be considered as consisting of three parts: low-level pol
<a name="build" />
### Building instructions
-Plupload depends on File API and XHR2 L2 pollyfills that currently have their [own repository](https://github.com/moxiecode/moxie) on GitHub. However in most cases you shouldn't care as we bundle the latest build of mOxie, including full and minified JavaScript source and pre-compiled `SWF` and `XAP` components, with the repository here. You can find everything you may need under `js/` folder.
+Plupload depends on File API and XHR2 L2 pollyfills that currently have their [own repository](https://github.com/moxiecode/moxie) on GitHub. However in most cases you shouldn't care as we bundled the latest build of mOxie, including full and minified JavaScript source and pre-compiled `SWF` and `XAP` components, with the repository here. You can find everything you may need under `js/` folder.
-But there are cases when you might need a custom build, for example free of unnecessary runtimes, half the original size, etc. Main complexity for this task is caused by the mOxie and its set of additional runtimes, that require special tools on your workstation in order to compile. Consider [build instructions for mOxie](#) - everything applies to Plupload as well.
+But there are cases when you might need a custom build, for example free of unnecessary runtimes, half the original size, etc. Main complexity for this task is caused by the mOxie and its set of additional runtimes, that require special tools on your workstation in order to compile. Consider [build instructions for mOxie](https://github.com/moxiecode/moxie#build-instructions) - everything applies to Plupload as well.
First of all, if you want to build custom Plupload packages you will require [Node.js](http://nodejs.org/), as this is our build environment of choice. Node.js binaries (as well as Source) [are available](http://nodejs.org/download/) for all major operating systems.

0 comments on commit df4b51f

Please sign in to comment.