cordova-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mwbro...@apache.org
Subject [1/6] Update 3.0.0 from edge directory.
Date Thu, 01 Aug 2013 22:11:35 GMT
Updated Branches:
  refs/heads/master 932e8c6cf -> 3fb6feae4


http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/guide/platforms/tizen/index.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/guide/platforms/tizen/index.md b/docs/en/3.0.0/guide/platforms/tizen/index.md
index 47130f0..8fb9570 100644
--- a/docs/en/3.0.0/guide/platforms/tizen/index.md
+++ b/docs/en/3.0.0/guide/platforms/tizen/index.md
@@ -63,13 +63,17 @@ Download the Tizen SDK from
 ## Open a Project in the SDK
 
 1. Launch the Tizen Eclipse IDE.
+
 2. Select __File → Import → Tizen Web Project__:
 
    ![](img/guide/platforms/tizen/import_project.png)
 
 3. Press __Next__.
+
 4. Make sure __Select root directory__ is checked.
+
 5. Make sure __Copy projects into workspace__ is checked.
+
 6. Press __Browse__ and select the Cordova Tizen `samples` project directory (such as `/cordova-basic`):
 
    ![](img/guide/platforms/tizen/import_widget.png)

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/guide/platforms/win8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/guide/platforms/win8/index.md b/docs/en/3.0.0/guide/platforms/win8/index.md
index 471793a..452e048 100644
--- a/docs/en/3.0.0/guide/platforms/win8/index.md
+++ b/docs/en/3.0.0/guide/platforms/win8/index.md
@@ -27,7 +27,7 @@ detailed platform-specific information:
 * Windows 8 Command-line Tools
 
 The command-line tools above refer to versions prior to Cordova 3.0.
-See The Cordova Command-line Interface for information about the
+See The Command-line Interface for information about the
 current interface.
 
 Microsoft deprecated the name _Metro-style apps_ in Windows 8 and
@@ -46,6 +46,7 @@ Follow the instructions [here](http://www.windowsstore.com/) to submit your apps
 ## 2. Install SDK + Cordova
 
 - Set up your preferred variant of Visual Studio 2012. All of the product's paid versions (Professional, etc.) let you build Windows Store apps. You need **Express for Windows 8** to build Windows Store apps using the [Express editions](http://www.microsoft.com/visualstudio/eng/products/visual-studio-express-products).
+
 - Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-8` subfolder.
 
 ## 3. Set up New Project
@@ -55,7 +56,8 @@ available in Windows Store apps. Use Cordova in Windows Store apps to
 expose the same APIs as on other Cordova-supported platforms.
 
 - Open Visual Studio 2012 and choose **New Project**.
-- Select **Installed → Template → Other Languages → JavaScript → Windows Store** from the tree, and then **Blank App** from the projects list. Enter whatever project name you like, such as **CordovaWin8Foo** as in this example.
+
+- Select **Installed → Template → Other Languages → JavaScript → Windows Store** from the tree, and then **Blank App** from the projects list. Enter whatever project name you like, such as `CordovaWin8Foo` as in this example.
 
     ![](img/guide/platforms/win8/wsnewproject.png)
 
@@ -63,7 +65,7 @@ expose the same APIs as on other Cordova-supported platforms.
 
 	![](img/guide/platforms/win8/wschangemanifest.png)
 
-- To include `cordova.js` in your project, right-click on the **js** folder in Solution Explorer and select **Add → New Item**. Locate the `cordova.js` file in the **lib\windows-8** folder noted above.
+- To include `cordova.js` in your project, right-click on the `js` directory in Solution Explorer and select **Add → New Item**. Locate the `cordova.js` file in the `lib\windows-8` directory noted above.
 
 - Edit the code for `index.html`. Add a reference to `cordova.js`. You can do this manually, or by dragging the file from Solution Explorer.
 

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/guide/platforms/win8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/guide/platforms/win8/tools.md b/docs/en/3.0.0/guide/platforms/win8/tools.md
index 9fbb26d..db2c68b 100644
--- a/docs/en/3.0.0/guide/platforms/win8/tools.md
+++ b/docs/en/3.0.0/guide/platforms/win8/tools.md
@@ -40,5 +40,7 @@ Commands must be run from a cmd or powershell prompt.
 Run the `create` command with the following parameters:
 
 * Path to your new Cordova Windows 8 project
-* Package Name, following reverse-domain style convention ( this becomes the default Namespace )
+
+* Package Name, following reverse-domain style convention. This becomes the default Namespace.
+
 * Project name

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/guide/platforms/win8/upgrading.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/guide/platforms/win8/upgrading.md b/docs/en/3.0.0/guide/platforms/win8/upgrading.md
index 102ad4a..3cb0e1c 100644
--- a/docs/en/3.0.0/guide/platforms/win8/upgrading.md
+++ b/docs/en/3.0.0/guide/platforms/win8/upgrading.md
@@ -21,8 +21,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
 
 This guide shows how to modify Windows 8 projects to upgrade from older versions of Cordova.
 Most of these instructions apply to projects created with an older set
-of command-line tools that precede the `cordova` CLI utility. See The
-Cordova Command-line Interface for information how to update the
+of command-line tools that precede the `cordova` CLI utility. See The Command-line Interface for information how to update the
 version of the CLI.
 
 ## Upgrade to 2.9.0 from 2.8.0 ##
@@ -30,7 +29,9 @@ version of the CLI.
 The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
 
 1. Remove `cordova-2.8.0.js` from the project's `www` directory.
-2. Add cordova.js file from the source to the project's `www` directory. (Note that the file no longer contains a version number in the filename.)
+
+2. Add `cordova.js` file from the source to the project's `www` directory. (Note that the file no longer contains a version number in the filename.)
+
 3. Build and test!
 
 ## Upgrade to 2.8.0 from 2.7.0 ##
@@ -38,5 +39,7 @@ The following commands should be done from within Visual Studio to be sure that
 The following commands should be done from within Visual Studio to be sure that the any project references are updated/deleted.
 
 1. Remove `cordova-2.7.0.js` from the project's `www` directory. 
-2. Add cordova.js file from the source to the project's `www` directory. (Note that the file no longer contains a version number in the filename.)
+
+2. Add `cordova.js` file from the source to the project's `www` directory. (Note that the file no longer contains a version number in the filename.)
+
 3. Build and test!

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/guide/platforms/wp7/index.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/guide/platforms/wp7/index.md b/docs/en/3.0.0/guide/platforms/wp7/index.md
index e26780d..f9851eb 100644
--- a/docs/en/3.0.0/guide/platforms/wp7/index.md
+++ b/docs/en/3.0.0/guide/platforms/wp7/index.md
@@ -33,7 +33,7 @@ applies to both versions:
 * Windows Phone Command-line Tools
 
 The command-line tools above refer to versions prior to Cordova 3.0.
-See The Cordova Command-line Interface for information about the
+See The Command-line Interface for information about the
 current interface.
 
 ## 1. System Requirements
@@ -50,7 +50,9 @@ __NOTE:__ Running the SDK in Virtual Machine might present some challenges. You
 ## 2. Install SDK + Cordova
 
 - Download and install the [Windows Phone SDK](http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27570/)
+
 - Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-phone-8\wp7` subfolder, `lib\windows-phone-8\wp8` contains the Windwos Phone 8 version of Cordova.
+
 - Copy the file CordovaWP7_x_x_x.zip to the folder : \My Documents\Visual Studio 2012\Templates\ProjectTemplates\
 
 ## 2.1. Building the template
@@ -61,8 +63,9 @@ In order to simplify the development process, Cordova comes with a script to bui
 
 ### Run the batch file to create and install the templates.
 
-- The root of the repo contains a file createTemplates.bat.  Double clicking this file will generate 2 .zip files. (CordovaWP7_x_x_x.zip + CordovaWP8_x_x_x.zip where x.x.x is the current version number)  To easily use these files in Visual Studio, copy them to 
+- The root of the repo contains a file createTemplates.bat.  Double clicking this file will generate 2 .zip files. (CordovaWP7_x_x_x.zip + CordovaWP8_x_x_x.zip where 3.0.0 is the current version number)  To easily use these files in Visual Studio, copy them to 
 "My Documents\Visual Studio 2012\Templates\ProjectTemplates\" You will then be able to create new Apache Cordova Windows Phone apps from the Visual Studio File->New Project menu.
+
 - If you run the batch file from the command line, you can also call with a parameter to install automatically
 
 Run the script :
@@ -72,13 +75,17 @@ Run the script :
 ## 3. Set up New Project
 
 - Open Visual Studio Express for Windows Phone and choose **New Project**.
+
 - Select **CordovaWP7**. (The version number is displayed in the template description.)
+
 - Give the project a name, and select __OK__.
 
 ## 4. Review the project structure
 
 - The `www` folder contains your Cordova `html/js/css` and any other resources included in your app.
+
 - Any content that you add here needs to be a part of the Visual Studio project, and it must be set as content.
+
 - Note: This screen capture was from the wp8 cordova-2.3.0 download, your listing will vary based on the actual version installed.
 
 ![](img/guide/platforms/wp8/projectStructure.png)
@@ -88,7 +95,9 @@ Run the script :
 In order to test your application on a device, the device must be registered. Click [here][register-url] to read documentation on deploying and testing on your Windows Phone 7.
 
 - Make sure your phone is connected, and the screen is unlocked.
+
 - In Visual Studio, select 'Device' from the top drop-down menu.
+
 - Press the green **play** button next to the main drop-down menu to start debugging, or type __F5__.
 
 ![](img/guide/platforms/wp7/wpd.png)

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/guide/platforms/wp8/index.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/guide/platforms/wp8/index.md b/docs/en/3.0.0/guide/platforms/wp8/index.md
index c45956f..13ef628 100644
--- a/docs/en/3.0.0/guide/platforms/wp8/index.md
+++ b/docs/en/3.0.0/guide/platforms/wp8/index.md
@@ -35,7 +35,7 @@ applies to both versions:
 * Windows Phone Command-line Tools
 
 The command-line tools above refer to versions prior to Cordova 3.0.
-See The Cordova Command-line Interface for information about the
+See The Command-line Interface for information about the
 current interface.
 
 ## 1. System Requirements
@@ -57,7 +57,7 @@ current interface.
         - See the [list of Intel processors that support VT-x (virtualization) and EPT (SLAT)](http://ark.intel.com/Products/VirtualizationTechnology)
     - Enable the virtualization capability (i.e., VT-x on Intel) in your BIOS settings, as usually this is disabled by default.
 
-- SDK + IDE ( Visual Studio )
+- SDK + IDE (Visual Studio)
     - Visual Studio 2012 Professional, Premium, or Ultimate. Note that Visual Studio Express for Windows Phone (included in the SDK) is not recommended because you can not build the template (see below) with VS Express, as it does not have the __Export Template__ functionality, which is only in VS Pro or higher.
 
 - Register and pay for a [Windows Phone Dev Center](http://dev.windowsphone.com/en-us/publish) account if you want to install your app on a real device or submit it to Market Place.
@@ -67,7 +67,9 @@ __NOTE:__ Running the SDK in Virtual Machine might present some challenges. You
 ## 2. Install SDK + Cordova
 
 - Download and install [Windows Phone SDK](http://www.microsoft.com/en-us/download/details.aspx?id=35471)
+
 - Download and extract the latest copy of [Cordova](http://phonegap.com/download). You will be working in the `lib\windows-phone-8\wp8` subfolder, `lib\windows-phone-8\wp7` contains the Windwos Phone 7 version of Cordova.
+
 - Copy the file CordovaWP8_x_x_x.zip to the folder : \My Documents\Visual Studio 2012\Templates\ProjectTemplates\
 
 ## 2.1. Building the template
@@ -78,8 +80,9 @@ In order to simplify the development process, Cordova comes with a script to bui
 
 ### Run the batch file to create and install the templates.
 
-- The root of the repo contains a file createTemplates.bat.  Double clicking this file will generate 2 .zip files. (CordovaWP7_x_x_x.zip + CordovaWP8_x_x_x.zip where x.x.x is the current version number)  To easily use these files in Visual Studio, copy them to 
+- The root of the repo contains a file createTemplates.bat.  Double clicking this file will generate 2 .zip files. (CordovaWP7_x_x_x.zip + CordovaWP8_x_x_x.zip where 3.0.0 is the current version number)  To easily use these files in Visual Studio, copy them to 
 "My Documents\Visual Studio 2012\Templates\ProjectTemplates\" You will then be able to create new Apache Cordova Windows Phone apps from the Visual Studio File->New Project menu.
+
 - If you run the batch file from the command line, you can also call with a parameter to install automatically
 
 Run the script :
@@ -89,7 +92,9 @@ Run the script :
 ## 3. Set up New Project
 
 - Open Visual Studio Express for Windows Phone and choose **New Project**.
+
 - Select **CordovaWP8**. (The version number is displayed in the template description.)
+
 - Give the project a name, and select __OK__.
 
 ![](img/guide/platforms/wp8/StandAloneTemplate.png)
@@ -97,7 +102,9 @@ Run the script :
 ## 4. Review the project structure
 
 - The `www` folder contains your Cordova `html/js/css` and any other resources included in your app.
+
 - Any content that you add here needs to be a part of the Visual Studio project, and it must be set as content.
+
 - Note: This screen capture was from the cordova-2.3.0 download, your listing will vary based on the actual version installed.
 
 ![](img/guide/platforms/wp8/projectStructure.png)
@@ -105,6 +112,7 @@ Run the script :
 ## 5. Build and Deploy to Emulator
 
 - Make sure **Windows Phone Emulator** is selected in the main drop-down menu.
+
 - Press the green **play** button next to the drop-down menu to start debugging, or type __F5__.
 
 ![](img/guide/platforms/wp8/BuildEmulator.png)
@@ -114,7 +122,9 @@ Run the script :
 In order to test your application on a device, the device must be registered. Click [here][register-url] to read documentation on deploying and testing on your Windows Phone 8.
 
 - Make sure your phone is connected, and the screen is unlocked.
+
 - In Visual Studio, select 'Device' from the top drop-down menu.
+
 - Press the green **play** button next to the main drop-down menu to start debugging, or type __F5__.
 
 ![](img/guide/platforms/wp7/wpd.png)

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/guide/platforms/wp8/plugin.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/guide/platforms/wp8/plugin.md b/docs/en/3.0.0/guide/platforms/wp8/plugin.md
index 3bf34b4..62d843e 100644
--- a/docs/en/3.0.0/guide/platforms/wp8/plugin.md
+++ b/docs/en/3.0.0/guide/platforms/wp8/plugin.md
@@ -27,8 +27,10 @@ and it comes with the majority of the 'plumbing' built for you already.
 
 1. Select your project, and right-click to choose __Add → New Item...__
     - Preferably add it to the 'Plugins' folder, but it is up to you
+
 2. Select 'Class' and name it `Echo.cs`
     - The name of this class must _exactly_ match what you call into `cordova.exec(win, fail, "Echo", ...)`
+
 3. Include the base classes implementation
 
         using WPCordovaClassLib.Cordova;
@@ -42,7 +44,7 @@ and it comes with the majority of the 'plumbing' built for you already.
             // ...
         }
 
-5. Add a method that is callable from JS
+5. Add a method that is callable from JavaScript
 
         public class Echo : BaseCommand
         {
@@ -74,7 +76,7 @@ your C# class like this:
         }
     }
 
-Then, in JS you need to call `exec` like this:
+Then, in JavaScript you need to call `exec` like this:
 
     cordova.exec(win, fail, "com.mydomain.cordovaExtensions.Echo", ...);
 
@@ -82,7 +84,7 @@ Then, in JS you need to call `exec` like this:
 
 The data received by your plugin method is a string value, but in actuality
 looking at our JavaScript code, we see our intention was to pass an array of strings.
-Looking back at our JS call to `cordova.exec`, we see we passed `[str]`:
+Looking back at our JavaScript call to `cordova.exec`, we see we passed `[str]`:
 
     cordova.exec(win, fail, "Echo", "echo", ["input string"]);
 
@@ -91,7 +93,7 @@ we see that the value is actually:
 
     "[\"input string\"]"
 
-All JavaScript exec arguments are JSON encoded before being passed into C#.
+All JavaScript `exec` arguments are JSON encoded before being passed into C#.
 
 If we want to treat this as the string we were expecting, we need to decode it.
 We can use simple JSON deserialization.
@@ -99,9 +101,9 @@ We can use simple JSON deserialization.
     string optVal = JsonHelper.Deserialize<string[]>(options)[0];
     // optVal now has the value of "input string"
 
-## Passing results from C# to JS
+## Passing results from C# to JavaScript
 
-The base class BaseCommand provides methods for passing data to your JS callback handlers.
+The base class BaseCommand provides methods for passing data to your JavaScript callback handlers.
 To simply signal that the command has succeeded, when no additional result info is needed,
 you can simply call:
 
@@ -111,7 +113,7 @@ To pass data back, you need to call a different version of `DispatchCommandResul
 
     DispatchCommandResult(new PluginResult(PluginResult.Status.OK, "Everything went as planned, this is a result that is passed to the success handler."));
 
-To pass structured object data back to JS, it should be encoded as a JSON string:
+To pass structured object data back to JavaScript, it should be encoded as a JSON string:
 
     DispatchCommandResult(new PluginResult(PluginResult.Status.OK, "{result:\"super awesome!\"}"));
 
@@ -144,11 +146,34 @@ in case we have bad input. This is a pattern used throughout the Cordova C# code
         // ... continue on to do our work
     }
 
+## Plugin XML
+
+These are windows phone specific examples of using the plugin.xml file, refer to the Plugin Specification for more details
+
+### `<source-file>`
+
+On windows phone the `<source-file>` element is currently used to define all plugin resources (ie. .cs, .xaml, .xaml.cs, .dll, image assets etc).
+
+### `<config-file>`
+
+The `<config-file>` element defines what elements get put into a config file. For example to add a plugin to the platforms config.xml, you would do something like this :
+
+    <config-file target="config.xml" parent="/*">
+        <feature name="PluginName">
+            <param name="wp-package" value="PluginName"/>
+        </feature>
+    </config-file>
+If we wanted to add the contacts capability to the WMAppManifest.xml, it would look like this :
+
+    <config-file target="Properties/WMAppManifest.xml" parent="/Deployment/App/Capabilities">
+        <Capability Name="ID_CAP_CONTACTS" />
+    </config-file>
+
 ## Advanced Plugin Functionality
 
 See other methods that you can override in:
 
-1. [BaseCommand.cs](https://github.com/apache/cordova-wp7/blob/master/templates/standalone/cordovalib/Commands/BaseCommand.cs)
+* [BaseCommand.cs](https://github.com/apache/cordova-wp7/blob/master/templates/standalone/cordovalib/Commands/BaseCommand.cs)
 
 For example, you can hook into the 'pause' and 'resume' application events.
 
@@ -182,6 +207,6 @@ inform yourself of errors.
 
 - It is usually a good idea to do parameter checking in your
   JavaScript code, before you call `exec`.  This allows you to re-use
-  more JavaScript code among your plug-in's various native
+  more JavaScript code among your plugin's various native
   implementations.
 

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/guide/platforms/wp8/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/guide/platforms/wp8/tools.md b/docs/en/3.0.0/guide/platforms/wp8/tools.md
index 2d96064..e688f3a 100644
--- a/docs/en/3.0.0/guide/platforms/wp8/tools.md
+++ b/docs/en/3.0.0/guide/platforms/wp8/tools.md
@@ -45,8 +45,9 @@ There are 2 ways to go about creating a new Apache Cordova WP7 or WP8 applicatio
 
 ### Run the batch file to create and install the templates.
 
-- The root of the repo contains a file createTemplates.bat.  Double clicking this file will generate 2 .zip files. (CordovaWP7_x_x_x.zip + CordovaWP8_x_x_x.zip where x.x.x is the current version number)  To easily use these files in Visual Studio, copy them to 
+- The root of the repo contains a file createTemplates.bat.  Double clicking this file will generate 2 .zip files. (CordovaWP7_x_x_x.zip + CordovaWP8_x_x_x.zip where 3.0.0 is the current version number)  To easily use these files in Visual Studio, copy them to 
 "My Documents\Visual Studio 2012\Templates\ProjectTemplates\" You will then be able to create new Apache Cordova Windows Phone apps from the Visual Studio File->New Project menu.
+
 - If you run the batch file from the command line, you can also call with a parameter to install automatically
 
 Run the script :
@@ -89,6 +90,7 @@ name.  Here is the syntax for both Windows Phone 7 and 8:
 Run the 'run' command with the following *optional* parameters
 
 * Target specification. This includes `--emulator`, `--device`, or `--target=<targetID>`.
+
 * Build specification. This includes `--debug`, `--release`, or `--nobuild`.
 
     $ C:\path\to\my_new_project\cordova\run [Target] [Build]

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/guide/platforms/wp8/upgrading.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/guide/platforms/wp8/upgrading.md b/docs/en/3.0.0/guide/platforms/wp8/upgrading.md
index bc58ba6..5cc09b1 100644
--- a/docs/en/3.0.0/guide/platforms/wp8/upgrading.md
+++ b/docs/en/3.0.0/guide/platforms/wp8/upgrading.md
@@ -20,38 +20,47 @@ license: Licensed to the Apache Software Foundation (ASF) under one
 # Upgrading Windows Phone
 
 This guide shows how to modify Windows Phone projects, both versions 7
-and 8, to upgrade from older versions of Cordova.
-Most of these instructions apply to projects created with an older set
-of command-line tools that precede the `cordova` CLI utility. See The
-Cordova Command-line Interface for information how to update the
-version of the CLI.
-The following section shows how to upgrade from non-CLI projects.
+and 8, to upgrade from older versions of Cordova.  Most of these
+instructions apply to projects created with an older set of
+command-line tools that precede the `cordova` CLI utility. See The
+Command-line Interface for information how to update the version of
+the CLI.  The following section shows how to upgrade from non-CLI
+projects.
 
 ## Upgrade to the CLI (3.0.0) from 2.9.0 ##
 
 1. Create a new Apache Cordova 3.0.0 project using the cordova CLI, as
-   described in The Cordova Command-line Interface.
+   described in The Command-line Interface.
+
 2. Add your platforms the the cordova project, for example: `cordova
    platform add wp7 wp8`.
-3. Copy the contents of the project's `www` folder to the `www` folder
+
+3. Copy the contents of the project's `www` directory to the `www` directory
    at the root of the cordova project you just created.
+
 4. Copy or overwrite any native assets from your original project
    (`SplashScreen`, `ApplicationIcon`, etc.), making sure to add any
    new files to the `.csproj` file. The windows phone project builds
    inside the `platforms\wp7` or `platforms\wp8` directory.
+
 5. Use the cordova CLI tool to install any plugins you need. Note that
    the CLI handles all core APIs as plugins, so they may need to be
    added. Only 3.0.0 plugins are compatible with the CLI.
+
 6. Build and test.
 
 ## Upgrade to 3.0.0 (non-CLI) from 2.9.0 ##
 
 In Visual Studio's Solution Explorer window:
 
-1. Create a new Apache Cordova WP7 or WP8 3.0.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
+1. Create a new Apache Cordova WP7 or WP8 3.0.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
 3. Copy and overwrite any splash screen, or icon images.
-4. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the VS project. 
+
+4. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project. 
+
 5. Build and test.
 
 __NOTE:__ all core APIs are removed from Cordova version 3.0, and must
@@ -63,92 +72,144 @@ Manage Plugins.
 
 In Visual Studio's Solution Explorer window:
 
-1. Create a new Apache Cordova WP7 or WP8 2.9.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
-3. Update the name of cordova.js in the HTML tag if it's still using cordova-VERSION.js (should be just cordova.js).
+1. Create a new Apache Cordova WP7 or WP8 2.9.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
+3. Update the name of `cordova.js` in the HTML tag if it's still using cordova-VERSION.js (should be just `cordova.js`).
+
 4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the .csproj file.
+
+5. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the .csproj file.
+
 6. Build and test.
 
 ## Upgrade to 2.8.0 from 2.7.0 ##
 
 In Visual Studio's Solution Explorer window:
 
-1. Create a new Apache Cordova WP7 or WP8 2.8.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
-3. Update your HTML to use the new cordova.js file. ( note that there is no longer a version number in the name )
+1. Create a new Apache Cordova WP7 or WP8 2.8.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
+3. Update your HTML to use the new `cordova.js` file. (Note the lack of a version number in the filename.)
+
 4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the VS project.
+
+5. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project.
+
 6. Build and test.
 
 ## Upgrade to 2.7.0 from 2.6.0 ##
 
 In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 or WP8 2.7.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
+
+1. Create a new Apache Cordova WP7 or WP8 2.7.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
 3. Update your HTML to use the new `cordova-2.7.0.js` file.
+
 4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the VS project.
+
+5. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project.
+
 6. Build and test.
 
 ## Upgrade to 2.6.0 from 2.5.0 ##
 
 In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 or WP8 2.6.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
+
+1. Create a new Apache Cordova WP7 or WP8 2.6.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
 3. Update your HTML to use the new `cordova-2.6.0.js` file.
+
 4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the VS project.
+
+5. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project.
+
 6. Build and test.
 
 ## Upgrade to 2.5.0 from 2.4.0 ##
 
 In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 or WP8 2.5.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
+
+1. Create a new Apache Cordova WP7 or WP8 2.5.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
 3. Update your HTML to use the new `cordova-2.5.0.js` file.
+
 4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the VS project.
+
+5. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project.
+
 6. Build and test.
 
 ## Upgrade to 2.4.0 from 2.3.0 ##
 
 In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 or WP8 2.4.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
+
+1. Create a new Apache Cordova WP7 or WP8 2.4.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
 3. Update your HTML to use the new `cordova-2.4.0.js` file.
+
 4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the VS project.
+
+5. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project.
+
 6. Build and test.
 
 ## Upgrade to 2.3.0 from 2.2.0 ##
 
 In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 2.3.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
+
+1. Create a new Apache Cordova WP7 2.3.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
 3. Update your HTML to use the new `cordova-2.3.0.js` file.
+
 4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the VS project.
+
+5. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project.
+
 6. Build and test.
 
 ## Upgrade to 2.2.0 from 2.1.0 ##
 
 In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 2.2.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
+
+1. Create a new Apache Cordova WP7 2.2.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
 3. Update your HTML to use the new `cordova-2.2.0.js` file.
+
 4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the VS project.
+
+5. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project.
+
 6. Build and test.
 
 ## Upgrade to 2.1.0 from 2.0.0 ##
 
 In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 2.1.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
+
+1. Create a new Apache Cordova WP7 2.1.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
 3. Update your HTML to use the new `cordova-2.1.0.js` file.
+
 4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the VS project.
+
+5. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project.
+
 6. Build and test.
 
 ## Upgrade to 2.0.0 from 1.9.0 ##
@@ -156,119 +217,185 @@ In Visual Studio's Solution Explorer window:
 There have been considerable changes to the WP7 project structure in Apache Cordova 2.0.0 which make this upgrade a little more involved that the others. Essentially this is not an upgrade but creation of a new project and copy over of existing source files.
 
 In Visual Studio's Solution Explorer window:
-1. Create a new Apache Cordova WP7 2.0 Project
-2. Copy the contents of your `www` folder to the new project, and be sure these items are added to the VS project.
+
+1. Create a new Apache Cordova WP7 2.0 Project.
+
+2. Copy the contents of your `www` directory to the new project, and be sure these items are added to the VS project.
+
 3. Update your HTML to use the new `cordova-2.0.0.js` file.
+
 4. Copy and overwrite any splash screen, or icon images.
-5. Copy over any plugins from the `plugins` folder to the new project and ensure that they are also added to the VS project.
+
+5. Copy over any plugins from the `plugins` directory to the new project and ensure that they are also added to the VS project.
+
 6. Build and test.
 
 ## Upgrade to 1.9.0 from 1.8.0 ##
 
 In Visual Studio's Solution Explorer window:
+
 1. Delete `GapLib/WP7CordovaClassLib.dll` from your project.
+
 2. Remove the reference to `WP7CordovaClassLib` in the __References__ folder.
-3. Right-click on __References__ and select __Add Reference__
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+
+3. Right-click on __References__ and select __Add Reference__.
+
+4. Navigate to the new distribution and add the file `WP7CordovaClassLib.dll`.
     - __NOTE:__ You can view the version of the DLL by right-clicking on the reference, and selecting __Properties__.
+
 5. Copy the new `cordova-1.9.0.js` into your project. (Be sure it is marked as Content.)
+
 6. Update your HTML to use the new `cordova-1.9.0.js` file.
 
 ## Upgrade to 1.8.0 from 1.7.0 ##
 
 In Visual Studio's Solution Explorer window:
+
 1. Delete `GapLib/WP7CordovaClassLib.dll` from your project.
+
 2. Remove the reference to `WP7CordovaClassLib` in the __References__ folder.
-3. Right-click on __References__ and select __Add Reference__
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+
+3. Right-click on __References__ and select __Add Reference__.
+
+4. Navigate to the new distribution and add the file `WP7CordovaClassLib.dll`.
     - __NOTE:__ You can view the version of the DLL by right-clicking on the reference, and selecting __Properties__.
+
 5. Copy the new `cordova-1.8.0.js` into your project. (Be sure it is marked as Content.)
+
 6. Update your HTML to use the new `cordova-1.8.0.js` file.
 
 ## Upgrade to 1.7.0 from 1.6.0 ##
 
 In Visual Studio's Solution Explorer window:
+
 1. Delete `GapLib/WP7CordovaClassLib.dll` from your project.
+
 2. Remove the reference to `WP7CordovaClassLib` in the __References__ folder.
-3. Right-click on __References__ and select __Add Reference__
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+
+3. Right-click on __References__ and select __Add Reference__.
+
+4. Navigate to the new distribution and add the file `WP7CordovaClassLib.dll`.
     - __NOTE:__ You can view the version of the DLL by right-clicking on the reference, and selecting __Properties__.
+
 5. Copy the new `cordova-1.7.0.js` into your project. (Be sure it is marked as Content.)
+
 6. Update your HTML to use the new `cordova-1.7.0.js` file.
 
 ## Upgrade to 1.6.1 from 1.6.0 ##
 
 In Visual Studio's Solution Explorer window:
+
 1. Delete `GapLib/WP7CordovaClassLib.dll` from your project.
+
 2. Remove the reference to `WP7CordovaClassLib` in the __References__ folder.
-3. Right-click on __References__ and select __Add Reference__
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+
+3. Right-click on __References__ and select __Add Reference__.
+
+4. Navigate to the new distribution and add the file `WP7CordovaClassLib.dll`.
     - __NOTE:__ You can view the version of the DLL by right-clicking on the reference, and selecting __Properties__.
+
 5. Copy the new `cordova-1.6.1.js` into your project. (Be sure it is marked as Content.)
+
 6. Update your HTML to use the new `cordova-1.6.1.js` file.
 
 ## Upgrade to 1.6.0 from 1.5.0 ##
 
 In Visual Studio's Solution Explorer window:
+
 1. Delete `GapLib/WP7CordovaClassLib.dll` from your project.
+
 2. Remove the reference to `WP7CordovaClassLib` in the __References__ folder.
-3. Right-click on __References__ and select __Add Reference__
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+
+3. Right-click on __References__ and select __Add Reference__.
+
+4. Navigate to the new distribution and add the file `WP7CordovaClassLib.dll`.
     - __NOTE:__ You can view the version of the DLL by right-clicking on the reference, and selecting __Properties__.
+
 5. Copy the new `cordova-1.6.0.js` into your project. (Be sure it is marked as Content.)
+
 6. Update your HTML to use the new `cordova-1.6.0.js` file.
 
 ## Upgrade to 1.5.0 from 1.4.0 ##
 
 In Visual Studio's Solution Explorer window:
+
 1. Delete `GapLib/WP7CordovaClassLib.dll` from your project.
+
 2. Remove the reference to `WP7CordovaClassLib` in the __References__ folder.
-3. Right-click on __References__ and select __Add Reference__
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+
+3. Right-click on __References__ and select __Add Reference__.
+
+4. Navigate to the new distribution and add the file `WP7CordovaClassLib.dll`.
     - __NOTE:__ You can view the version of the DLL by right-clicking on the reference, and selecting __Properties__.
+
 5. Copy the new `cordova-1.5.0.js` into your project. (Be sure it is marked as Content.)
+
 6. Update your HTML to use the new `cordova-1.5.0.js` file.
 
 ## Upgrade to 1.4.0 from 1.3.0 ##
 
 In Visual Studio's Solution Explorer window:
+
 1. Delete `GapLib/WP7CordovaClassLib.dll` from your project.
+
 2. Remove the reference to `WP7CordovaClassLib` in the __References__ folder.
-3. Right-click on __References__ and select __Add Reference__
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+
+3. Right-click on __References__ and select __Add Reference__.
+
+4. Navigate to the new distribution and add the file `WP7CordovaClassLib.dll`.
     - __NOTE:__ You can view the version of the DLL by right-clicking on the reference, and selecting __Properties__.
+
 5. Copy the new `cordova-1.4.0.js` into your project. (Be sure it is marked as Content.)
+
 6. Update your HTML to use the new `cordova-1.4.0.js` file.
 
 ## Upgrade to 1.3.0 from 1.2.0 ##
 
 In Visual Studio's Solution Explorer window:
+
 1. Delete `GapLib/WP7CordovaClassLib.dll` from your project.
+
 2. Remove the reference to `WP7CordovaClassLib` in the __References__ folder.
-3. Right-click on __References__ and select __Add Reference__
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+
+3. Right-click on __References__ and select __Add Reference__.
+
+4. Navigate to the new distribution and add the file `WP7CordovaClassLib.dll`.
     - __NOTE:__ You can view the version of the DLL by right-clicking on the reference, and selecting __Properties__.
+
 5. Copy the new `cordova-1.3.0.js` into your project. (Be sure it is marked as Content.)
+
 6. Update your HTML to use the new `cordova-1.3.0.js` file.
 
 ## Upgrade to 1.2.0 from 1.1.0 ##
 
 In Visual Studio's Solution Explorer window:
+
 1. Delete `GapLib/WP7CordovaClassLib.dll` from your project.
+
 2. Remove the reference to `WP7CordovaClassLib` in the __References__ folder.
-3. Right-click on __References__ and select __Add Reference__
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+
+3. Right-click on __References__ and select __Add Reference__.
+
+4. Navigate to the new distribution and add the file `WP7CordovaClassLib.dll`.
     - __NOTE:__ You can view the version of the DLL by right-clicking on the reference, and selecting __Properties__.
+
 5. Copy the new `cordova-1.2.0.js` into your project. (Be sure it is marked as Content.)
+
 6. Update your HTML to use the new `cordova-1.2.0.js` file.
 
 ## Upgrade to 1.1.0 from 1.0.0 ##
 
 In Visual Studio's Solution Explorer window:
+
 1. Delete `GapLib/WP7CordovaClassLib.dll` from your project.
+
 2. Remove the reference to `WP7CordovaClassLib` in the __References__ folder.
-3. Right-click on __References__ and select __Add Reference__
-4. Navigate to the new distribution and add the file 'WP7CordovaClassLib.dll'
+
+3. Right-click on __References__ and select __Add Reference__.
+
+4. Navigate to the new distribution and add the file `WP7CordovaClassLib.dll`.
     - __NOTE:__ you can view the version of the DLL by right-clicking on the reference, and selecting __Properties__.
+
 5. Copy the new `cordova-1.1.0.js` into your project. (Be sure it is marked as Content.)
+
 6. Update your HTML to use the new `cordova-1.1.0.js` file.

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/index.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/index.md b/docs/en/3.0.0/index.md
index d89fd8e..42f5aa4 100644
--- a/docs/en/3.0.0/index.md
+++ b/docs/en/3.0.0/index.md
@@ -31,7 +31,7 @@ license: Licensed to the Apache Software Foundation (ASF) under one
         </li>
         <li>
             <h2>Platform Guides</h2>
-            <span>Set up each SDK to create your first app.</span>
+            <span>Set up each SDK and update projects</span>
         </li>
         <li>
             <h2>Configuration Reference</h2>

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/3fb6feae/docs/en/3.0.0/plugin_ref/spec.md
----------------------------------------------------------------------
diff --git a/docs/en/3.0.0/plugin_ref/spec.md b/docs/en/3.0.0/plugin_ref/spec.md
index 63b9b0c..685998d 100644
--- a/docs/en/3.0.0/plugin_ref/spec.md
+++ b/docs/en/3.0.0/plugin_ref/spec.md
@@ -32,7 +32,7 @@ A sample plugin element:
         id="com.alunny.foo"
         version="1.0.2">
 
-## &lt;plugin&gt; element
+## `<plugin>` element
 
 The `plugin` element is the plugin manifest's top-level element. It
 features the following attributes:
@@ -51,9 +51,9 @@ features the following attributes:
   A version number for the plugin, that matches the following
   major-minor-patch style regular expression:
 
-    ^\d+[.]\d+[.]\d+$
+        ^\d+[.]\d+[.]\d+$
 
-## &lt;engines&gt; and &lt;engine&gt; elements
+## `<engines>` and `<engine>` elements
 
 The child elements of the `<engines>` element specify versions of
 Apache Cordova-based frameworks that this plugin supports. An example:
@@ -68,7 +68,7 @@ Similar to the `<plugin>` element's `version` attribute, the specified
 version string should match a major-minor-patch string conforming to
 the regular expression:
 
-    ^\d+[.]\d+[.]\d+$
+        ^\d+[.]\d+[.]\d+$
 
 Engine elements may also specify fuzzy matches to avoid repetition,
 and to reduce maintenance when the underlying platform is updated.
@@ -86,7 +86,7 @@ project does not meet the engine's constraints.
 If no `<engine>` tags are specified, plugman attempts to install into
 the specified cordova project directory blindly.
 
-## &lt;name&gt; element
+## `<name>` element
 
 A human-readable name for the plugin, whose text content contains the
 name of the plugin. For example:
@@ -95,7 +95,35 @@ name of the plugin. For example:
 
 This element does not (yet) handle localization.
 
-## &lt;asset&gt; element
+## `<description>` element
+
+A human-readable description for the plugin. The text content of the element contains
+the description of the plugin. An example:
+
+    <description>Foo plugin description</description>
+
+This element does not (yet) handle localization.
+
+## `<author>` element
+
+Plugin author name. The text content of the element contains
+the name of the plugin author. An example:
+
+    <author>Foo plugin description</author>
+
+## `<keywords>` element
+
+Plugin keywords. The text content of the element contains comma separated keywords to describe the plugin. An example:
+
+    <keywords>foo,bar</keywords>
+
+## `<license>` element
+
+Plugin license. The text content of the element contains the plugin license. An example:
+
+    <license>Apache 2.0 License</license>
+
+## `<asset>` element
 
 One or more elements listing the files or directories to be copied
 into a Cordova app's `www` directory. Examples:
@@ -132,7 +160,7 @@ platform-specific web assets, as described below. Attributes include:
   issues a notification about the conflict, and exits with a non-zero
   code.
 
-## &lt;js-module&gt; element
+## `<js-module>` element
 
 Most plugins include one or more JavaScript files.  Each `<js-module>`
 tag corresponds to a JavaScript file, and prevents the plugin's users
@@ -169,18 +197,18 @@ Details for the `<js-module>` tag:
 
 * Three tags are allowed within `<js-module>`:
 
-    * `<clobbers target="some.value" />` indicates that the
+    * `<clobbers target="some.value"/>` indicates that the
       `module.exports` is inserted into the `window` object as
       `window.some.value`. You can have as many `<clobbers>` as you
       like. Any object not available on `window` is created.
 
-    * `<merges target="some.value" />` indicates that the module
+    * `<merges target="some.value"/>` indicates that the module
       should be merged with any existing value at `window.some.value`.
       If any key already exists, the module's version overrides the
       original. You can have as many `<merges>` as you like. Any
       object not available on `window` is created.
 
-    * `<runs />` means that your code should be specified with
+    * `<runs/>` means that your code should be specified with
       `cordova.require`, but not installed on the `window`
       object. This is useful when initializing the module, attaching
       event handlers or otherwise. You can only have up to one
@@ -198,7 +226,7 @@ exits with a non-zero code.
 Nesting `<js-module>` elements within `<platform>` declares
 platform-specific JavaScript module bindings.
 
-## &lt;dependency&gt;
+## `<dependency>`
 
 The `<dependency>` tag allows you specify other plugins on which the
 current plugin depends. While future versions will access them from
@@ -240,7 +268,7 @@ installed the plugin with a local path directly to it. Plugman finds
 the root of the git repository and then finds the other plugin from
 there.
 
-## &lt;platform&gt;
+## `<platform>`
 
 The `<platform>` tag identifies platforms that have associated native
 code or require modifications to their configuration files. Tools
@@ -271,7 +299,7 @@ chosen, are listed:
 * wp7
 * wp8
 
-## &lt;source-file&gt;
+## `<source-file>`
 
 The `<source-file>` element identifies executable source code that
 should be installed into a project. Examples:
@@ -312,7 +340,7 @@ It supports the following attributes:
   If set, assigns the specified compiler flags for the particular
   source file.
 
-## &lt;config-file&gt;
+## `<config-file>`
 
 Identifies an XML-based configuration file to be modified, where in
 that document the modification should take place, and what should be
@@ -375,7 +403,7 @@ It supports the following attributes:
   document, the tool stops and reverses the installation process,
   issues a warning, and exits with a non-zero code.
 
-## &lt;plugins-plist&gt;
+## `<plugins-plist>`
 
 This is _outdated_ as it only applies to cordova-ios 2.2.0 and
 below. Use the `<config-file>` tag for newer versions of Cordova.
@@ -391,7 +419,7 @@ file in an iOS Cordova project. For example:
 
     <plugins-plist key="Foo" string="CDVFoo" />
 
-## &lt;resource-file&gt; and &lt;header-file&gt;
+## `<resource-file>` and `<header-file>`
 
 Like source files, but specifically for platforms such as iOS that
 distinguish between source files, headers, and resources.  Examples:
@@ -400,7 +428,7 @@ distinguish between source files, headers, and resources.  Examples:
     <resource-file src="CDVFooViewController.xib" />
     <header-file src="CDVFoo.h" />
 
-## &lt;lib-file&gt;
+## `<lib-file>`
 
 Like source, resource, and header files, but specifically for
 platforms such as BlackBerry 10 that use user-generated libraries.
@@ -420,7 +448,7 @@ Supported attributes:
 * `arch`: The architecture for which the `.so` file has been built,
   either `device` or `simulator`.
 
-## &lt;framework&gt;
+## `<framework>`
 
 Identifies a framework (usually part of the OS/platform) on which the plugin depends.
 
@@ -429,9 +457,6 @@ Examples:
     <framework src="libsqlite3.dylib" />
     <framework src="social.framework" weak="true" />
 
-
-
-
 The `src` attribute identifies the framework, which plugman attempts
 to add to the Cordova project, in the correct fashion for a given
 platform.
@@ -439,7 +464,7 @@ platform.
 The optional `weak` attribute is a boolean indicating whether the
 framework should be weakly linked. The default is `false`.
 
-## &lt;info&gt;
+## `<info>`
 
 Additional information provided to users. This is useful when you
 require extra steps that can't be easily automated or are beyond


Mime
View raw message