Added a new custom plugin screenshot and made a couple minor adjustme…

…nts to formatting.
phonegap · Apr 13, 2016 · 7a6ef38 · 7a6ef38
1 parent a384161
commit 7a6ef38
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 8 deletions.
diff --git a/docs/3-references/browser-support/4-custom-plugins.html.md b/docs/3-references/browser-support/4-custom-plugins.html.md
@@ -14,14 14,13 @@ To support the browser in your own plugins, follow the [Cordova Plugin Developme
 and ensure you've defined the `browser` platform handling in your `plugin.xml` mapping. You will define your JavaScript files 
 to implement your specific `browser` platform handling code in the `src/browser`
 path in your plugin root. For instance:
-
- ![](/images/browser-support/browser-folder.png)
-
 
  <img class="mobile-image" src="/images/browser-support/custom-plugin.png"/>
 
 You'll need to ensure you name these browser platform-specific JS files with different names then the client-side implementation included in the `www` by default. Most of the Apache Cordova plugins add the word `Proxy` to the
  class. You can take a look at any of the [Apache Cordova core plugins](/plugin-apis/) for specific examples. 
 
-For instance, by taking a look at the Apache Cordova Camera Plugin's [plugin.xml](https://github.com/apache/cordova-plugin-camera/blob/master/plugin.xml), 
 For instance, by taking a look at the Apache Cordova Camera [plugin.xml](https://github.com/apache/cordova-plugin-camera/blob/master/plugin.xml), 
 you will see how the `CameraProxy.js` class is defined with the following:
 
  <!-- browser -->
@@ -37,6 36,6 @@ you will see how the `CameraProxy.js` class is defined with the following:
   </js-module>
  </platform>
   
-<div class="info">The `<runs/>` element is required to tell Cordova to initialize the module.</div> 
 <div class="alert--tip">**Tip:** The `<runs/>` element is required to tell Cordova to initialize the module.</div> 
   
 <div class="alert--info">**Note:** Browser Support for the PhoneGap Desktop App will be released in the very near future.</div> 
diff --git a/docs/3-references/browser-support/5-caution-next-steps.html.md b/docs/3-references/browser-support/5-caution-next-steps.html.md
@@ -14,8 14,7 @@ are listed below:
 and between platforms. You should refer to the [Can I Use](http://caniuse.com) site for specific details of which features your 
 apps use and what is supported.
 
-![](/images/browser-support/caniuse.png)
-
  ![](/images/browser-support/caniuse.png) 
 - The browser does not have a soft keyboard to test with so you cannot test the effect it might have on the UI/screen layout when 
 using form controls/input fields.
 - Certain devices may support hardware features that cannot be tested in a desktop browser.
@@ -25,7 24,6 @@ using form controls/input fields.
  situations like incoming/outgoing calls, texts, notifications cannot be properly tested in the browser.
 
 
-
 ### Development/Testing Options:
 1. Use the browser to develop as much of your app as possible with the tooling you already know and use daily while being aware of the limitations
 noted above. 

diff --git a/public/images/browser-support/custom-plugin.png b/public/images/browser-support/custom-plugin.png