fixed relative links on documents (#712)

* fixed relative link

* fixed ja, cn, ko, pt_BR

Author: ytakahashi

Diff for: docs/cn/faqs.md

@@ -33,7 +33,7 @@
 
 ## 在哪里放置我的静态资源？
 
-[**静态资源的使用**](/using-static-assets.md)
+[**静态资源的使用**](using-static-assets.md)
 
 ## 为什么 `npm run lint` 会出现错误？
 

Diff for: docs/cn/testing.md

@@ -26,4 +26,4 @@ npm test
 
 ### 关于 CI 测试
 
-如果在脚手架时你决定使用 `electron-builder` 作为构建工具，那么你可以在针对 `darwin`、`linux` 和 `win32` 的 Travis CI 以及 AppVeyor 上轻松测试你的程序。在 `.travis.yml` 和 `appveyor.yml` 两者之间，你会发现一些被注释掉的部分，你可以快速取消注释以启用测试。确保阅读 [**使用 CI 的自动化部署**](/using-electron-builder.md#automated-deployments-using-ci) 上的更多信息。
+如果在脚手架时你决定使用 `electron-builder` 作为构建工具，那么你可以在针对 `darwin`、`linux` 和 `win32` 的 Travis CI 以及 AppVeyor 上轻松测试你的程序。在 `.travis.yml` 和 `appveyor.yml` 两者之间，你会发现一些被注释掉的部分，你可以快速取消注释以启用测试。确保阅读 [**使用 CI 的自动化部署**](using-electron-builder.md#automated-deployments-using-ci) 上的更多信息。

Diff for: docs/en/faqs.md

@@ -33,7 +33,7 @@ Make sure to close and reopen the developer tools panel on first launch if they
 
 ## Where do I put Static Assets?
 
-[**Using Static Assets**](/using-static-assets.md)
+[**Using Static Assets**](using-static-assets.md)
 
 ## Why did `npm run lint` end with an error?
 

Diff for: docs/en/testing.md

@@ -26,5 +26,5 @@ npm test
 
 ### On the subject of CI testing
 
-If your decided to use `electron-builder` as your build tool when scaffolding, then you can easily test your application on both Travis CI & AppVeyor for `darwin`, `linux`, and `win32`. Inside both `.travis.yml` and `appveyor.yml` you will find commented sections you can quickly un-comment to enable testing. Make sure to read up on [**Automated Deployments using CI**](/using-electron-builder.md#automated-deployments-using-ci)** **for further information.
+If your decided to use `electron-builder` as your build tool when scaffolding, then you can easily test your application on both Travis CI & AppVeyor for `darwin`, `linux`, and `win32`. Inside both `.travis.yml` and `appveyor.yml` you will find commented sections you can quickly un-comment to enable testing. Make sure to read up on [**Automated Deployments using CI**](using-electron-builder.md#automated-deployments-using-ci)** **for further information.
 

Diff for: docs/ja/faqs.md

@@ -33,7 +33,7 @@
 
 ## 静的なアセットはどこに置けば良いですか？
 
-[**静的なアセットの使用**](/using-static-assets.md)
+[**静的なアセットの使用**](using-static-assets.md)
 
 ## `npm run lint` がエラーで終了するのはなぜですか？
 

Diff for: docs/ja/testing.md

@@ -26,4 +26,4 @@ npm test
 
 ### CI テストについて
 
-スキャフォールディング時にビルドツールとして `electron-builder` を使うことに決めた場合、`darwin`、`linux`、`win32`向けにTravis CI と AppVeyorの両方で簡単にアプリケーションをテストできます。`.travis.yml` と `appveyor.yml` の中には、コメントアウトされたセクションがあります。テストを有効にするために、セクションのコメントアウトを解除することができます。詳細については、[**CI を使用した自動デプロイ**](/using-electron-builder.md#automated-deployments-using-ci)を読んでください。** **
+スキャフォールディング時にビルドツールとして `electron-builder` を使うことに決めた場合、`darwin`、`linux`、`win32`向けにTravis CI と AppVeyorの両方で簡単にアプリケーションをテストできます。`.travis.yml` と `appveyor.yml` の中には、コメントアウトされたセクションがあります。テストを有効にするために、セクションのコメントアウトを解除することができます。詳細については、[**CI を使用した自動デプロイ**](using-electron-builder.md#automated-deployments-using-ci)を読んでください。** **

Diff for: docs/ko/faqs.md

@@ -33,7 +33,7 @@ Make sure to close and reopen the developer tools panel on first launch if they
 
 ## Where do I put Static Assets?
 
-[**Using Static Assets**](/using-static-assets.md)
+[**Using Static Assets**](using-static-assets.md)
 
 ## Why did `npm run lint` end with an error?
 

Diff for: docs/ko/testing.md

@@ -27,5 +27,5 @@ npm test
 
 ### CI 테스팅에 관하여
 
-스캐폴딩 할 때 `electron-builder`를 빌드 도구로 사용하기로 결정했다면 `darwin`, `linux` 그리고 `win32` 용 Travis CI 및 AppVeyor에서 애플리케이션을 쉽게 테스트 할 수 있습니다. `.travis.yml` 와 `appveyor.yml` 둘 다 내부에서 주석 처리 된 섹션을 찾을 수 있고 곧바로 주석을 해제하여 테스트를 수행 할 수 있습니다. 자세한 내용은 [**Automated Deployments using CI**](/using-electron-builder.md#automated-deployments-using-ci)를 읽으세요.
+스캐폴딩 할 때 `electron-builder`를 빌드 도구로 사용하기로 결정했다면 `darwin`, `linux` 그리고 `win32` 용 Travis CI 및 AppVeyor에서 애플리케이션을 쉽게 테스트 할 수 있습니다. `.travis.yml` 와 `appveyor.yml` 둘 다 내부에서 주석 처리 된 섹션을 찾을 수 있고 곧바로 주석을 해제하여 테스트를 수행 할 수 있습니다. 자세한 내용은 [**Automated Deployments using CI**](using-electron-builder.md#automated-deployments-using-ci)를 읽으세요.
 

Diff for: docs/pt_BR/faqs.md

@@ -39,7 +39,7 @@ Make sure to close and reopen the developer tools panel on first launch if they
 
 ## Onde eu coloco meus assets estaticos ?
 
-[**Usando Static(estatico) Assets**](/using-static-assets.md)
+[**Usando Static(estatico) Assets**](using-static-assets.md)
 
 ## Por que o `npm run lint` resulta em um erro ?
 

Diff for: docs/pt_BR/testing.md

@@ -26,5 +26,5 @@ npm test
 
 ### On the subject of CI testing
 
-If your decided to use `electron-builder` as your build tool when scaffolding, then you can easily test your application on both Travis CI & AppVeyor for `darwin`, `linux`, and `win32`. Inside both `.travis.yml` and `appveyor.yml` you will find commented sections you can quickly un-comment to enable testing. Make sure to read up on [**Automated Deployments using CI**](/using-electron-builder.md#automated-deployments-using-ci)** **for further information.
+If your decided to use `electron-builder` as your build tool when scaffolding, then you can easily test your application on both Travis CI & AppVeyor for `darwin`, `linux`, and `win32`. Inside both `.travis.yml` and `appveyor.yml` you will find commented sections you can quickly un-comment to enable testing. Make sure to read up on [**Automated Deployments using CI**](using-electron-builder.md#automated-deployments-using-ci)** **for further information.