cordova-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mwbro...@apache.org
Subject [4/4] docs commit: [CB-3822] First pass at BlackBerry guide update.
Date Tue, 16 Jul 2013 20:54:51 GMT
[CB-3822] First pass at BlackBerry guide update.

Conflicts:

	docs/en/edge/guide/platforms/blackberry10/index.md
	docs/en/edge/guide/platforms/blackberry10/tools.md


Project: http://git-wip-us.apache.org/repos/asf/cordova-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/e99ea818
Tree: http://git-wip-us.apache.org/repos/asf/cordova-docs/tree/e99ea818
Diff: http://git-wip-us.apache.org/repos/asf/cordova-docs/diff/e99ea818

Branch: refs/heads/master
Commit: e99ea818ae996c4530efdfc686c049deeea39dc4
Parents: a6cb620
Author: Mike Sierra <letmespellitoutforyou@gmail.com>
Authored: Wed Jul 10 13:43:21 2013 -0400
Committer: Michael Brooks <michael@michaelbrooks.ca>
Committed: Tue Jul 16 13:54:26 2013 -0700

----------------------------------------------------------------------
 docs/en/edge/guide/platforms/android/index.md   |   2 +-
 .../edge/guide/platforms/android/upgrading.md   |   2 +-
 .../guide/platforms/blackberry/upgrading.md     |   4 +-
 .../edge/guide/platforms/blackberry10/index.md  | 399 ++++++++++---------
 .../edge/guide/platforms/blackberry10/tools.md  |  62 ++-
 docs/en/edge/guide/platforms/tizen/index.md     |   2 +-
 docs/en/edge/guide/platforms/wp8/plugin.md      |   2 +-
 7 files changed, 243 insertions(+), 230 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e99ea818/docs/en/edge/guide/platforms/android/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/android/index.md b/docs/en/edge/guide/platforms/android/index.md
index 71b171e..7b544c5 100644
--- a/docs/en/edge/guide/platforms/android/index.md
+++ b/docs/en/edge/guide/platforms/android/index.md
@@ -38,7 +38,7 @@ NOTE, doc said:
 - Android 3.x (Deprecated May 2013)
 -->
 
-Developers should use the the `cordova` utility in conjunction with
+Developers should use the `cordova` utility in conjunction with
 the Android SDK.  See The Command-line Interface for
 information how to install it, add projects, then build and deploy a
 project.

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e99ea818/docs/en/edge/guide/platforms/android/upgrading.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/android/upgrading.md b/docs/en/edge/guide/platforms/android/upgrading.md
index 63019d3..4428ccb 100644
--- a/docs/en/edge/guide/platforms/android/upgrading.md
+++ b/docs/en/edge/guide/platforms/android/upgrading.md
@@ -120,7 +120,7 @@ This document is for people who need to upgrade their Cordova versions
from an o
 
 ### Notes about 2.0.0 release
 config.xml will be replacing cordova.xml and plugins.xml.  This new file is a combination
of the previous two.  However, the
-old files are deprecated, and and while currently still work, will cease working in a future
release.
+old files are deprecated, and while currently still work, will cease working in a future
release.
 
 ## Upgrade to 1.9.0 from 1.8.1 ##
 

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e99ea818/docs/en/edge/guide/platforms/blackberry/upgrading.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry/upgrading.md b/docs/en/edge/guide/platforms/blackberry/upgrading.md
index df0daa7..4e02b0c 100644
--- a/docs/en/edge/guide/platforms/blackberry/upgrading.md
+++ b/docs/en/edge/guide/platforms/blackberry/upgrading.md
@@ -93,7 +93,7 @@ However, here are the new parts needed for the piecemeal update:
 1. Update the cordova.blackberry.js file in the ‘Phonegap-2.6.0/lib/blackberry/javascript’
folder
 2. Update the ‘ext’, ‘ext-air’, and ‘ext-qnx’ in the ‘Phonegap-2.6.0/lib/blackberry/framework’
folder
 3. Update the ‘build.xml’ file in the ‘Phonegap-2.6.0/lib/blackberry’ folder
-4. Update the the ‘Phonegap-2.6.0/lib/blackberry/bin’ folder
+4. Update the ‘Phonegap-2.6.0/lib/blackberry/bin’ folder
 5. Update the ‘VERSION’ file in the ‘Phonegap-2.6.0/lib/blackberry’ folder
 
 Updating the example/ folder or migrating an existing project:
@@ -115,7 +115,7 @@ However, here are the new parts needed for the piecemeal update:
 1. Update the cordova.blackberry.js file in the ‘Phonegap-2.5.0/lib/blackberry/javascript’
folder
 2. Update the ‘ext’, ‘ext-air’, and ‘ext-qnx’ in the ‘Phonegap-2.5.0/lib/blackberry/framework’
folder
 3. Update the ‘build.xml’ file in the ‘Phonegap-2.5.0/lib/blackberry’ folder
-4. Update the the ‘Phonegap-2.5.0/lib/blackberry/bin’ folder
+4. Update the ‘Phonegap-2.5.0/lib/blackberry/bin’ folder
 5. Update the ‘VERSION’ file in the ‘Phonegap-2.5.0/lib/blackberry’ folder
 
 Updating the example/ folder or migrating an existing project:

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e99ea818/docs/en/edge/guide/platforms/blackberry10/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry10/index.md b/docs/en/edge/guide/platforms/blackberry10/index.md
index 1eae034..312feca 100644
--- a/docs/en/edge/guide/platforms/blackberry10/index.md
+++ b/docs/en/edge/guide/platforms/blackberry10/index.md
@@ -1,185 +1,214 @@
----
-license: Licensed to the Apache Software Foundation (ASF) under one
-         or more contributor license agreements.  See the NOTICE file
-         distributed with this work for additional information
-         regarding copyright ownership.  The ASF licenses this file
-         to you under the Apache License, Version 2.0 (the
-         "License"); you may not use this file except in compliance
-         with the License.  You may obtain a copy of the License at
-
-           http://www.apache.org/licenses/LICENSE-2.0
-
-         Unless required by applicable law or agreed to in writing,
-         software distributed under the License is distributed on an
-         "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-         KIND, either express or implied.  See the License for the
-         specific language governing permissions and limitations
-         under the License.
----
-
-BlackBerry 10 Platform Guide
-==================================
-
-Apache Cordova is an application development platform that allows you to use common web technologies,
primarily HTML5, JavaScript, and CSS, to create applications for mobile devices. Cordova uses
a standard set of APIs to access common device features. Additional plugins allow you to access
BlackBerry specific APIs, so that you can extend your application to tightly integrate with
the BlackBerry 10 OS.
-
-Requirements
-------------
-
-Cordova for BlackBerry has the following software requirements:
-
--   Windows XP (32-bit) or Windows 7 (32-bit and 64-bit) or Mac OSX 10.6.4+
--   node.js (> 0.9.9) [Download node.js now](http://nodejs.org/)
--   BlackBerry 10 Native SDK. [Download the BlackBerry 10 Native SDK now.](http://developer.blackberry.com/native/download/)
-
-Setting up your signing keys
-----------------------------
-
-Before starting development, you'll need to register for your code signing key and debug
token. The signing key allows you to sign your completed app so that you can distribute it
through BlackBerry World. The debug token allows you to test an unsigned app on a BlackBerry
10 device. You do not need to create and install the debug token yourself; if you supply the
keystore password, the build script will create and install the debug token for you.
-
--   [Register for your code signing key now.](https://www.blackberry.com/SignedKeys/codesigning.html)
--   [Set your computer up for code signing. ](http://developer.blackberry.com/html5/documentation/set_up_for_signing.html)
--   [Learn more about debug tokens.](http://developer.blackberry.com/html5/documentation/running_your_bb10_app_2008471_11.html)
-
-Creating your project
--------------------------
-
-To create a new project, you use the `create` command to set up the folder structure for
your app.
-
-1.  On the command line, navigate to the folder where you extracted Cordova.
-2.  Run the `create` command using the following syntax:
-    ```
-	bin/create <path-to-project>
-	```
-
-This command creates the folder structure for your project at the specified location. All
of your project resource files should be stored in the *<path-to-project>*/www folder,
or in a subfolder within it.
-
-Adding and managing targets
----------------------------
-
-A target refers to a BlackBerry device or emulator that you will use to test your app. Targets
are added directly to your project; you can add multiple targets to your project, each with
a unique name. Then, when you want to deploy your app to a particular target, you can simply
refer to that target by name when you run your script.
-
-###Add a target
-
-To add a target, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/target  add  <name>  <ip-address>  [-t <device
| simulator>]  [-p | --password <password>]  [--pin <device-pin>]
-```
-
-where
-
--   `<name>`  specifies a unique name for the target.
--   `<ip-address>`  specifies the ip address of the BlackBerry device or emulator.
--   `-t <device | simulator>` specifies the target type. If not provided, the default
value is device.
--   `-p|--password <password>`  specifies the password for the device or emulator.
This is required only if the device or emulator is password protected.
--   `--pin <device-pin>`  specifies the PIN of the BlackBerry device, which identifies
that device as a valid host for the debug token. This argument is required only if you are
creating a debug token.
-
-###Remove a target
-
-To remove a target, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/target  remove  <name>
-```
-
-###Set a target as the default
-
-To specify a specific target as the default, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/target  default  <name>
-```
-
-Building your app
------------------
-
-To build your app, run the build script. You can build the app in either release mode or
in debug mode.
-
--   When you build the app in release mode, you are preparing it for distribution through
BlackBerry World. The script packages your app resources and plugins together in a .bar file,
then signs the app.
--   When you build the app in debug mode, you are preparing it to be tested. The script packages
your app resources and plugins together in a .bar file, but does not sign it. The script can
also deploy the app onto a previously defined target. If you have not already created and
installed a debug token, you can supply the keystore password, and the build script will create
and install the debug token for you as well.
-
-    Debug mode also enables Web Inspector for the app, which allows you to remotely inspect
the source code. A prompt displays the URL that you can use to connect to and inspect your
app. For more information on using Web Inspector, see [Debugging using Web Inspector](http://developer.blackberry.com/html5/documentation/web_inspector_overview_1553586_11.html).
-
-###Build your app in release mode
-
-To build your app in release mode, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/build  release  -k|--keystorepass <password>  [-b|--buildId
<number>]  [-p|--params <params-JSON-file>]
-```
-
-where
-
--   `-k|--keystorepass <password>`  specifies the password you defined when you configured
your computer to sign applications.
--   `-b|--buildId <number>`  specifies the build version number of your application.
Typically, this number should be incremented from the previous signed version. This argument
is optional.
--   `-p|--params <params-JSON-file>`  specifies a JSON file containing additional parameters
to pass to downstream tools. This argument is optional.
-
-###Build your app in debug mode
-
-To build your app in release mode, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/build  debug  [<target>]  [-k|--keystorepass <password>]
 [-p|--params <params-JSON-file>]  [-ll|--loglevel <error|warn|verbose>]
-```
-
-where
-
--   `<target>`  specifies the name of a previously added target. If `<target>`
 is not specified, the default target is used, if one has been created. This argument is only
required if you want the script to deploy your app to a BlackBerry device or emulator and
you have not created a default target. Additionally, if `<target>`  is a device, then
that device must be connected to your computer by USB connection or be connected to the same
Wi-Fi network as your computer.
--   `-k|--keystorepass <password>`  specifies the password you defined when you configured
your computer to sign applications. This password is also used to create your debug token.
This argument is only required if you want the script to create and install the debug token
for you.
--   `-p|--params <params-JSON-file>`  specifies a JSON file containing additional parameters
to pass to downstream tools.
--   `-ll|--loglevel <level>`  specifies the log level. The log level may be one of
`error`, `warn`, or `verbose`.
-
-Note that all of these parameters are optional. If you have previously defined a default
target (and installed a debug token, if that target is a BlackBerry device), you can run the
script with no arguments, and the script will package your app and deploy it to the default
target. For example:
-
-```
-<path-to-project>/cordova/build debug
-```
-
-Deploying an app
--------------------------
-
-You can test your app using either a BlackBerry device or an emulator. Before deploying your
app, you must first create a target for the device or emulator you want to deploy your app
to.
-
-The run script will first build  your app. If you intend to deploy an app to a physical device
for testing, you must first install a debug token on that device. If you specify the `--keystorepass
<password>` argument when running the run script, the script will create and install
the debug token for you. You do not need a debug token to test your app on an emulator, even
if that app is unsigned.
-
-To deploy your app to a device or emulator, on a command line type the following command:
-
-```
-<path-to-project>/cordova/run <target> [--no-build]
-```
-
-where
--   `<target>`  specifies the name of a previously added target. If `<target>`
 is a device, then that device must be connected to your computer by USB connection or be
connected to the same Wi-Fi network as your computer.
-
--   `-no--build` will use the most recently built version of the application rather than
re-building. This is useful to test an application in release mode.
-
-Adding and managing plugins
----------------------------
-
-To add additional functionality that is outside of the core features of Cordova, you'll need
to add plugins. A plugin represents a set of APIs that provide access to additional features
of the platform.
-
-In order to use a plugin, you must first add it into your project. Once added into your project,
the plugin will be bundled with your project during the build process, to ensure that your
app has access to all the APIs it needs.
-
-###Add a plugin
-
-To add a plugin, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/plugin add <path to plugin>
-```
-
-###Remove a plugin
-
-To remove a plugin, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/plugin rm <name>
-```
-
-###View a list of installed plugins
-
-To view a list of installed plugins, on the command line, type the following command:
-
-```
-<path-to-project>/cordova/plugin ls
-```
+BlackBerry 10 Platform Guide
+==================================
+
+This guide describes how to set up your SDK development environment to
+deploy Cordova apps for Blackberry 10 devices.
+
+## Requirements and Support
+
+The development environment is available on Windows XP (32-bit),
+Windows 7 (32-bit or 64-bit), or Mac OS X 10.6.4+.
+
+Developers should use the `cordova` utility in conjunction with the
+Blackberry 10 SDK.  See The Command-line Interface for information how
+to install it, add projects, then build and deploy a project.
+
+You can use the Cordova CLI to develop Blackberry 10 projects.  For
+previous versions of Blackberry, you need to use a different set of
+command-line tools, described in BlackBerry Platform Guide.
+
+## Install the SDK
+
+The BlackBerry 10 Native SDK is available from
+[developer.blackberry.com](http://developer.blackberry.com/native/download/).
+
+Along with the SDK, you also need to register for a code signing key
+and debug token.  The signing key allows you to distribute apps
+through BlackBerry World. The debug token allows you to test unsigned
+apps on a BlackBerry 10 emulator or device. You do not need to create
+and install the debug token yourself; if you supply the keystore
+password, the build script creates and installs the debug token for
+you. For more information:
+
+* [Register for your code signing key.](https://www.blackberry.com/SignedKeys/codesigning.html)
+
+* [Set up your computer for code signing.](http://developer.blackberry.com/html5/documentation/set_up_for_signing.html)
+
+* [Learn more about debug tokens.](http://developer.blackberry.com/html5/documentation/running_your_bb10_app_2008471_11.html)
+
+## Create a Project
+
+Use the `cordova` utility to set up a new project, as described in The
+Cordova The Command-line Interface. For example, in a source-code
+directory:
+
+        $ cordova create hello com.example.hello "Hello World"
+        $ cd hello
+        $ cordova platform add blackberry
+        $ cordova build
+
+## Deploy to Emulator
+
+To test an app either on an emulator or a device, you need to add a
+_target_ to your project. Each is identified with a unique name, and
+associated with an IP address.  The following associates a target
+named _simu_ with _0.0.0.0_. The `-t` option specifies the `simulator`
+target _type_:
+
+        $ platforms/blackberry/cordova/target add simu 0.0.0.0 -t simulator
+        $ platforms/blackberry/cordova/target default simu
+
+## Deploy to Device
+
+To deploy to a device, make sure it is plugged into your computer,
+then run a variation of the `target` command such as this:
+
+        $ platforms/blackberry/cordova/target add dev 0.0.0.0 -t device -p unlockme --pin
123456
+
+The `--pin` option refers to whatever password you set up when
+requesting a signing key, as described above.  The `-p` option refers
+to whatever local password locks the device itself.
+
+Full `target` syntax follows:
+
+        $ cordova/target add <name> <ip-address> [-t <device | simulator>]
[-p | --password <password>] [--pin <device-pin>]
+
+where:
+
+* `<name>` specifies a unique name for the target.
+
+* `<ip-address>` specifies the ip address of the BlackBerry device or
+  simulator.
+
+* `-t <device | simulator>` specifies the target type. If not
+  provided, the default value is device.
+
+* `-p|--password <password>` specifies the password for the device or
+  simulator. This is required only if the device or simulator is
+  password protected.
+
+* `--pin <device-pin>` specifies the PIN of the BlackBerry device,
+  which identifies that device as a valid host for the debug
+  token. This argument is required only if you are creating a debug
+  token.
+
+To remove a target:
+
+        $ cordova/target remove <name>
+
+To set a target as the default:
+
+        $ cordova/target default <name>
+
+<!--
+
+## Building your app
+
+To build your app, run the build script. You can build the app in
+either release mode or in debug mode.
+
+* When you build the app in release mode, you are preparing it for
+  distribution through BlackBerry World. The script packages your app
+  resources and plugins together in a _.bar_ file, then signs the app.
+
+* When you build the app in debug mode, you are preparing it to be
+  tested. The script packages your app resources and plugins together
+  in a _.bar_ file, but does not sign it. The script can also deploy
+  the app onto a previously defined target. If you have not already
+  created and installed a debug token, you can supply the keystore
+  password, and the build script will create and install the debug
+  token for you as well.
+
+Debug mode also enables Web Inspector for the app, which allows you to
+remotely inspect the source code. A prompt displays the URL that you
+can use to connect to and inspect your app. For more information on
+using Web Inspector, see [Debugging using Web
+Inspector](http://developer.blackberry.com/html5/documentation/web_inspector_overview_1553586_11.html).
+
+### Build your app in release mode
+
+To build your app in release mode, type the following command:
+
+        $ cordova/build release -k|--keystorepass <password> [-b|--buildId <number>]
[-p|--params <params-JSON-file>]
+
+where
+
+* `-k|--keystorepass <password>` specifies the password you defined
+  when you configured your computer to sign applications.
+
+* `-b|--buildId <number>` specifies the build version number of your
+  application. Typically, this number should be incremented from the
+  previous signed version. This argument is optional.
+
+* `-p|--params <params-JSON-file>` specifies a JSON file containing
+  additional parameters to pass to downstream tools. This argument is
+  optional.
+
+### Build your app in debug mode
+
+To build your app in release mode, on the command line, type the
+following command:
+
+        $ cordova/build debug [<target>] [-k|--keystorepass <password>] [-p|--params
<params-JSON-file>] [-ll|--loglevel <error|warn|verbose>]
+
+where
+
+* `<target>` specifies the name of a previously added target. If
+  `<target>` is not specified, the default target is used, if one has
+  been created. This argument is only required if you want the script
+  to deploy your app to a BlackBerry device or simulator and you have
+  not created a default target. Additionally, if `<target>` is a
+  device, then that device must be connected to your computer by USB
+  connection or be connected to the same Wi-Fi network as your
+  computer.
+
+* `-k|--keystorepass <password>` specifies the password you defined
+  when you configured your computer to sign applications. This
+  password is also used to create your debug token. This argument is
+  only required if you want the script to create and install the debug
+  token for you.
+
+* `-p|--params <params-JSON-file>` specifies a JSON file containing
+  additional parameters to pass to downstream tools.
+
+* `-ll|--loglevel <level>` specifies the log level. The log level may
+  be one of `error`, `warn`, or `verbose`.
+
+Note that all of these parameters are optional. If you have previously
+defined a default target (and installed a debug token, if that target
+is a BlackBerry device), you can run the script with no arguments, and
+the script will package your app and deploy it to the default
+target. For example:
+
+        $ cordova/build debug
+
+## Deploying an app
+
+You can test your app using either a BlackBerry device or a simulator.
+Before deploying your app, you must first create a target for the
+device or simulator you want to deploy your app to.
+
+The run script will first build your app. If you intend to deploy an
+app to a physical device for testing, you must first install a debug
+token on that device. If you specify the `--keystorepass <password>`
+argument when running the run script, the script will create and
+install the debug token for you. You do not need a debug token to test
+your app on a simulator, even if that app is unsigned.
+
+To deploy your app to a device or simulator, on a command line type
+the following command:
+
+        $ cordova/run <target> [--no-build]
+
+where:
+
+* `<target>` specifies the name of a previously added target. If
+  `<target>` is a device, then that device must be connected to your
+  computer by USB connection or be connected to the same Wi-Fi network
+  as your computer.
+
+* `-no--build` will use the most recently built version of the
+  application rather than re-building. This is useful to test an
+  application in release mode.
+
+-->

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e99ea818/docs/en/edge/guide/platforms/blackberry10/tools.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/blackberry10/tools.md b/docs/en/edge/guide/platforms/blackberry10/tools.md
index 7b3b5a1..b6a868f 100644
--- a/docs/en/edge/guide/platforms/blackberry10/tools.md
+++ b/docs/en/edge/guide/platforms/blackberry10/tools.md
@@ -39,9 +39,7 @@ arguments.
 
 The 'create' command creates a new project:
 
-```
-bin/create <path-to-project>
-```
+    bin/create <path-to-project>
 
 ## target
 
@@ -51,18 +49,19 @@ target, or set a target as the default target.
 
 ### Add a target
 
-```
-<path-to-project>/cordova/target  add  <name>  <ip-address>  <device
| simulator>  [-p | --password <password>]  [--pin <device-pin>]
-```
+    <path-to-project>/cordova/target add <name> <ip-address> <device
| simulator> [-p | --password <password>] [--pin <device-pin>]
 
 where
 
 - `<name>` specifies a unique name for the target.
+
 - `<ip-address>` specifies the ip address of the BlackBerry device or
-  emulator.
+  simulator.
+
 - `-p|--password <password>` specifies the password for the device or
   emulator. This is required only if the device or emulator is
   password protected.
+
 - `--pin <device-pin>` specifies the PIN of the BlackBerry device,
   which identifies that device as a valid host for the debug
   token. This argument is required only if you are creating a debug
@@ -70,15 +69,11 @@ where
 
 ### Remove a target
 
-```
-<path-to-project>/cordova/target  remove  <name>
-```
+    <path-to-project>/cordova/target  remove  <name>
 
 ### Set a target as the default
 
-```
-<path-to-project>/cordova/target  default  <name>
-```
+    <path-to-project>/cordova/target  default  <name>
 
 ## build
 
@@ -88,10 +83,9 @@ in debug mode (which produces an unsigned .bar file).
 
 ### Build your project in release mode
 
-```
-<path-to-project>/cordova/build  release  -k|--keystorepass <password>  [-b|--buildId
<number>]  [-p|--params <params-JSON-file>]
-```
-where
+    <path-to-project>/cordova/build  release  -k|--keystorepass <password>  [-b|--buildId
<number>]  [-p|--params <params-JSON-file>]
+
+where:
 
 -   `-k|--keystorepass <password>`  specifies the password you defined when you configured
your computer to sign applications.
 -   `-b|--buildId <number>`  specifies the build version number of your application.
Typically, this number should be incremented from the previous signed version. This argument
is optional.
@@ -99,9 +93,7 @@ where
 
 ### Build your project in debug mode
 
-```
-<path-to-project>/cordova/build  debug  [<target>]  [-k|--keystorepass <password>]
 [-p|--params <params-JSON-file>]  [-ll|--loglevel <error|warn|verbose>]
-```
+    <path-to-project>/cordova/build  debug  [<target>]  [-k|--keystorepass <password>]
 [-p|--params <params-JSON-file>]  [-ll|--loglevel <error|warn|verbose>]
 
 where
 
@@ -113,13 +105,16 @@ where
   device, then that device must be connected to your computer by USB
   connection or be connected to the same Wi-Fi network as your
   computer.
+
 - `-k|--keystorepass <password>` specifies the password you defined
   when you configured your computer to sign applications. This
   password is also used to create your debug token. This argument is
   only required if you want the script to create and install the debug
   token for you.
+
 - `-p|--params <params-JSON-file>` specifies a JSON file containing
   additional parameters to pass to downstream tools.
+
 - `-ll|--loglevel <level>` specifies the log level. The log level may
   be one of `error`, `warn`, or `verbose`.
 
@@ -128,9 +123,7 @@ installed a debug token, if that target is a BlackBerry device), you
 can run the script with no arguments, and the script will package your
 app and deploy it to the default target. For example:
 
-```
-<path-to-project>/cordova/build debug
-```
+    <path-to-project>/cordova/build debug
 
 ## run
 
@@ -139,9 +132,7 @@ or an emulator. Before deploying your app, you must first create a
 target for the device or emulator you want to deploy your app to. The
 deploy script will deploy the most recent build of your app.
 
-```
-<path-to-project>/cordova/run <target>
-```
+    <path-to-project>/cordova/run <target>
 
 where
 
@@ -154,26 +145,19 @@ where
 
 The `target` command allows you to add and remove plugins
 
-### Fetch a locally-hosted plugin
+### Fetch a locally hosted plugin
 
-```
-<path-to-project>/cordova/plugin fetch <path-to-plugin>
-```
+    <path-to-project>/cordova/plugin fetch <path-to-plugin>
 
 ### View a list of installed plugins
 
-```
-<path-to-project>/cordova/plugin ls
-```
+    <path-to-project>/cordova/plugin ls
 
 ### Add a plugin
 
-```
-<path-to-project>/cordova/plugin add <name>
-```
+    <path-to-project>/cordova/plugin add <name>
 
 ### Remove a plugin
 
-```
-<path-to-project>/cordova/plugin rm <name>
-```
+    <path-to-project>/cordova/plugin rm <name>
+

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e99ea818/docs/en/edge/guide/platforms/tizen/index.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/tizen/index.md b/docs/en/edge/guide/platforms/tizen/index.md
index 9a594a3..3571501 100644
--- a/docs/en/edge/guide/platforms/tizen/index.md
+++ b/docs/en/edge/guide/platforms/tizen/index.md
@@ -25,7 +25,7 @@ Tizen Platform Guide
 the Tizen SDK requires Linux Ubuntu 10.04/10.10/11.04/11.10 (32-bit),
 or Windows XP SP3/7 (32-bit).
 
-Developers should use the the `cordova` utility in conjunction with
+Developers should use the `cordova` utility in conjunction with
 the Tizen SDK.  See The Command-line Interface for information
 how to install it, add projects, then build and deploy a project.
 

http://git-wip-us.apache.org/repos/asf/cordova-docs/blob/e99ea818/docs/en/edge/guide/platforms/wp8/plugin.md
----------------------------------------------------------------------
diff --git a/docs/en/edge/guide/platforms/wp8/plugin.md b/docs/en/edge/guide/platforms/wp8/plugin.md
index ed89361..81040c6 100644
--- a/docs/en/edge/guide/platforms/wp8/plugin.md
+++ b/docs/en/edge/guide/platforms/wp8/plugin.md
@@ -107,7 +107,7 @@ Passing results from C# to JS
 
 The base class BaseCommand provides methods for passing data to your JS callback handlers.
 To simply signal that the command has succeeded, when no additional result info is needed,
-you can can simply call:
+you can simply call:
 
     DispatchCommandResult(); // calls back with an empty plugin result, considered a success
callback
 


Mime
View raw message