Merge pull request appium#2408 from bootstraponline/master

Update links to pass lint

docs/cn/hybrid.cn.md

@@ -2,8 +2,8 @@
 
 Appium 其中一个理念就是你不能为了测试应用而修改应用。为了符合这个方法学，我们可以使用 Selenium 测试传统 web 应用的方法来测试混合 web 应用 (比如，iOS 应用里的元素 "UIWebView" )，这是有可能的。这里会有一些技术性的复杂，Appium 需要知道你是想测试原生部分呢还是web部分。幸运的是，我们还能遵守 WebDriver 的协议。
 
-*  [混合 iOS 应用](#ios)
-*  [混合 Android 应用](#android)
+*  [混合 iOS 应用](hybrid.cn.md#ios)
+*  [混合 Android 应用](hybrid.cn.md#android)
 
 ## 自动化混合 iOS 应用
 

docs/cn/troubleshooting.cn.md

@@ -4,7 +4,7 @@
 
 ## 一般问题
 
-* 确保你是根据 [README](README) 里面的入门指南按部就班的。
+* 确保你是根据 [README](README.md) 里面的入门指南按部就班的。
 * 确保你的系统配置好了(比如， xCode 是最新的，Android SDK 安装好了， `ANDROID_HOME` 配置好了，参照 [setup instructions](https://github.com/appium/appium/blob/master/docs/running-on-osx.md) ).
 * 确保你应用的路径正确。
 

docs/en/hybrid.md

@@ -8,8 +8,8 @@ required so that Appium knows whether you want to automate the native aspects
  of the app or the web views, but thankfully, we can stay within the
  WebDriver protocol for everything.
 
-*  [Hybrid iOS apps](#ios)
-*  [Hybrid Android apps](#android)
+*  [Hybrid iOS apps](hybrid.md#automating-hybrid-ios-apps)
+*  [Hybrid Android apps](hybrid.md#automating-hybrid-android-apps)
 
 ## Automating hybrid iOS apps
 

docs/en/intro.md

@@ -15,7 +15,7 @@ multiple platforms (iOS, Android), using the same API. This enables a large
 or total amount of code reuse between iOS and Android testsuites.
 
 For specific information about what it means for Appium to "support" its
-platforms, version, and automation modalities, please see the [platform support doc](platform-support).
+platforms, version, and automation modalities, please see the [platform support doc](platform-support.md).
 
 ## Appium Philosophy
 
@@ -94,7 +94,7 @@ For example, we might set the `platformName` capability to `iOS` to tell
 Appium that we want an iOS session, rather than an Android one. Or we might
 set the `safariAllowPopups` capability to `true` in order to ensure that,
 during a Safari automation session, we're allowed to use JavaScript to open
-up new windows. See the [capabilities doc](caps) for the complete list of
+up new windows. See the [capabilities doc](caps.md) for the complete list of
 capabilities available for Appium.
 
 *Appium Server*
@@ -111,5 +111,5 @@ very handy when writing tests!
 ## Getting Started
 
 Congratulations! You are now armed with enough knowledge to begin using
-Appium. Why not head back to the [getting started doc](getting-started) for
+Appium. Why not head back to the [getting started doc](getting-started.md) for
 more detailed requirements and instructions?

docs/en/mobile-web.md

@@ -37,7 +37,7 @@ run the ios-webkit-debug-proxy against your iOS device.
 ### Setup
 
 Before you can run your tests against Safari on a real device you will need to:
-* Have the **ios-webkit-debug-proxy** installed and running (see the [hybrid docs](hybrid)  for instructions)
+* Have the **ios-webkit-debug-proxy** installed and running (see the [hybrid docs](hybrid.md) for instructions)
 * Turn on **web inspector** on iOS device (**settings > safari >
 advanced**, only for iOS 6.0 and up)
 * Create a **provisioning profile** that can be used to deploy the SafariLauncherApp.

docs/en/platform-support.md

@@ -6,7 +6,7 @@ make explicit the level of support and requirements for each of these.
 
 ## iOS Support
 
-See [Running on OS X: iOS](running-on-osx#ios) for iOS requirements and setup instructions.
+See [Running on OS X: iOS](running-on-osx.md) for iOS requirements and setup instructions.
 
 * Versions: 6.1, 7.0, and 7.1
 * Devices: iPhone Simulator, iPad Simulator, and real iPhones and iPads
@@ -15,17 +15,17 @@ See [Running on OS X: iOS](running-on-osx#ios) for iOS requirements and setup in
   Apple's [UIAutomation](https://developer.apple.com/library/ios/documentation/DeveloperTools/Reference/UIAutomationRef/_index.html) framework.
 * Mobile web support: Yes, via automation of mobile Safari. For real devices,
   ios-webkit-remote-debugger is required, and automation of native aspects of
-  the Safari interface is not possible. See the [mobile web doc](mobile-web) for instructions.
+  the Safari interface is not possible. See the [mobile web doc](mobile-web.md) for instructions.
 * Hybrid support: Yes. For real devices, ios-webkit-remote-debugger is
-  required. See the [hybrid doc](hybrid) for instructions.
+  required. See the [hybrid doc](hybrid.md) for instructions.
 * Support for automating multiple apps in one session: No
 * Support for automating multiple devices simultaneously: No
 * Support for automating vendor-provided or third-party apps: Only
   vendor-provided apps (Preferences, Maps, etc...), and only on the simulator
 
 ## Android Support
 
-See [Running on OS X: Android](running-on-osx#android), [Running on Windows](running-on-windows), or [Running on Linux](running-on-linux) for Android requirements and setup instructions.
+See [Running on OS X: Android](running-on-osx.md#android), [Running on Windows](running-on-windows.md), or [Running on Linux](running-on-linux.md) for Android requirements and setup instructions.
 
 * Versions: 2.3 and up
   * Versions 4.2 and up are supported via Appium's own [UiAutomator](http://developer.android.com/tools/help/uiautomator/index.html)
@@ -43,15 +43,15 @@ See [Running on OS X: Android](running-on-osx#android), [Running on Windows](run
   server as a proxy. With 4.2 and 4.3, automation works on official Chrome
   browser or Chromium only. With 4.4+, automation also works on the built-in
   "Browser" app. Chrome/Chromium/Browser must already be installed on the
-  device under test. See the [mobile web doc](mobile-web) for instructions.
-* Hybrid support: Yes. See the [hybrid doc](hybrid) for instructions.
+  device under test. See the [mobile web doc](mobile-web.md) for instructions.
+* Hybrid support: Yes. See the [hybrid doc](hybrid.md) for instructions.
   * With default Appium automation backend: versions 4.4 and up
   * With Selendroid automation backend: versions 2.3 and up
 * Support for automating multiple apps in one session: Yes (but not when
   using the Selendroid backend)
 * Support for automating multiple devices simultaneously: Yes,
   though Appium must be started using different ports for the server
   parameters `--port`, `--bootstrap-port` (or `--selendroid-port`) and/or
-  `--chromedriver-port`. See the [server args doc](server-args) for more information on these parameters.
+  `--chromedriver-port`. See the [server args doc](server-args.md) for more information on these parameters.
 * Support for automating vendor-provided or third-party apps: Yes (but not
   when using the Selendroid backend)

docs/en/running-on-linux.md

@@ -32,11 +32,11 @@ line using node.js:
 
     node .
 
-See the [server documentation](server-args) for all the command line arguments.
+See the [server documentation](server-args.md) for all the command line arguments.
 
 ## Notes
 
 * There exists a hardware accelerated emulator for android, it has it's own
   limitations. For more information you can check out this
-  [page](android-hax-emulator).
+  [page](android-hax-emulator.md).
 * Make sure that `hw.battery=yes` in your AVD's `config.ini`.

docs/en/running-on-osx.md

@@ -67,4 +67,4 @@ To go back to iOS 7.0 testing.
 * Make sure that `hw.battery=yes` in your AVD's `config.ini`.
 * There exists a hardware accelerated emulator for android, it has its own
   limitations. For more information you can check out this
-  [page](android-hax-emulator).
+  [page](android-hax-emulator.md).

docs/en/running-on-windows.md

@@ -41,7 +41,7 @@ To run tests on Windows, you will need to have the Android Emulator booted or
 
     node .
 
-See the [server documentation](server-args)
+See the [server documentation](server-args.md)
 for all the command line arguments.
 
 ## Notes
@@ -50,5 +50,5 @@ for all the command line arguments.
   to work on Windows.
 * There exists a hardware accelerated emulator for android, it has it's own
   limitations. For more information you can check out this
-  [page](android-hax-emulator).
+  [page](android-hax-emulator.md).
 * Make sure that `hw.battery=yes` in your AVD's `config.ini`.

docs/en/running-tests.md

@@ -56,9 +56,9 @@ First, make sure you have one and only one Android emulator or device
 connected. If you run `adb devices`, for example, you should see one device
 connected. This is the device Appium will use for tests. Of course, to have
 a device connected, you'll need to have made an Android AVD (see system
-setup ([Windows](running-on-windows#setup),
-[Mac](running-on-osx#android),
-or [Linux](running-on-linux#setup))
+setup ([Windows](running-on-windows.md),
+[Mac](running-on-osx.md),
+or [Linux](running-on-linux.md)
 for more information). If the Android SDK tools are on your path, you can
 simply run:
 

docs/en/touch-actions.md

@@ -36,4 +36,4 @@ Currently Appium support some of the gestures in the Touch Actions API:
 * single tap
 
 Some other gestures are supported through the "Alternative access method"
-explained in [Automating mobile gestures](gestures)
+explained in [Automating mobile gestures](gestures.md)

docs/en/troubleshooting.md

@@ -8,7 +8,7 @@ to github or write to the appium-discuss mailing list.
 * Make sure you've followed the getting started steps in the [README](https://github.com/appium/appium/blob/master/README.md)
 * Make sure your system is set up appropriately (i.e., XCode is updated,
   Android SDK is installed and `ANDROID_HOME` is set:
-  [setup instructions](running-on-osx))
+  [setup instructions](running-on-osx.md)
 * Make sure the paths to your applications are correct
 
 ## If you're running Appium.app
@@ -42,7 +42,7 @@ own items in the SDK manager. Make sure you install the build-tools and platform
 * It's sometimes useful to run `adb kill-server && adb devices`. This can
   reset the connection to the Android device.
 * Make sure you know about the `app-package`, `app-activity`,
-  and `app-wait-activity` desiredCapabilities (see [this doc](running-tests#run-android)
+  and `app-wait-activity` desiredCapabilities (see [this doc](running-tests.md)
   for more information).
 * Make sure you set ANDROID_HOME pointing to the Android SDK directory
 
@@ -104,7 +104,7 @@ output when it's run in verbose mode so that we can diagnose what's going on.
 * Sometimes iOS UI elements become invalidated milliseconds after they are
   found. This results in an error that looks like `(null) cannot be tapped`.
   Sometimes the only solution is to put the finding-and-acting code in a retry
-  block. See also `mobile: findAndAct` on the [finding elements doc page](finding-elements)
+  block. See also `mobile: findAndAct` on the [finding elements doc page](finding-elements.md)
 * Appium may have difficulties finding the `node` executable if you've
 installed Node and npm via MacPorts. You must make sure that the MacPorts bin
  folder (`/opt/local/bin` by default) is added to `PATH` somewhere in your