Clean up config file locations

content/_code-samples/checks/cli/sign-cancel-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Jan-24 01:11:07 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/sign-cash-exact-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Jan-24 01:17:54 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/sign-cash-flex-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Apr-03 00:09:53 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/sign-create-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Mar-21 21:00:05 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/submit-cancel-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Jan-24 01:11:07 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/submit-cash-exact-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Jan-24 01:17:54 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/submit-cash-flex-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Apr-03 00:10:30 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/submit-create-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Mar-28 01:52:49 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/tx-cancel-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Jan-24 01:11:53 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/tx-cash-exact-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Jan-24 01:18:39 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/tx-cash-flex-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Apr-03 00:11:17 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/_code-samples/checks/cli/tx-create-resp.txt

@@ -1,4 +1,4 @@
-Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+Loading: "/etc/opt/ripple/rippled.cfg"
 2018-Mar-28 02:17:55 HTTPClient:NFO Connecting to 127.0.0.1:5005
 
 {

content/tutorials/manage-account-settings/set-up-multi-signing.ja.md

@@ -34,7 +34,7 @@
 複数のXRP Ledgerキーセット（アドレスとシークレット）をSignerListのメンバーに追加する必要があります。SignerListには、レジャーに既存の資金供給のあるアドレス、または[wallet_proposeメソッド][]で生成した新しいアドレスを追加できます。例:
 
     $ rippled wallet_propose
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
         "result" : {
@@ -88,7 +88,7 @@
     >         }
     >     ]
     > }'
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" : {
@@ -143,7 +143,7 @@
 スタンドアロンモードで`rippled`を実行している場合は、[ledger_acceptメソッド][]を使用してレジャーを手動で閉鎖します。
 
     $ rippled ledger_accept
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" : {
@@ -160,7 +160,7 @@
 通常、アカウントは異なるタイプのオブジェクト（トラストラインやオファーなど）を複数所有できます。このチュートリアルで新しいアドレスに資金を供給した場合、SignerListが応答の唯一のオブジェクトになります。
 
     $ rippled account_objects rEuLyBCvcw4CFmzv8RepSiAoNgF8tTGJQC validated
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" : {

content/tutorials/manage-account-settings/set-up-multi-signing.md

@@ -31,7 +31,7 @@ You need one or more validly-formed XRP Ledger addresses to include as members o
 You can generate new addresses using the [wallet_propose method][]. For example:
 
     $ rippled wallet_propose
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
         "result" : {
@@ -85,7 +85,7 @@ In this example, the SignerList has 3 members, with the weights and quorum set u
     >         }
     >     ]
     > }'
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" : {
@@ -145,7 +145,7 @@ Use the [account_objects method][] to confirm that the SignerList is associated
 Normally, an account can own many objects of different types (such as trust lines and offers). If you funded a new address for this tutorial, the SignerList is the only object in the response.
 
     $ rippled account_objects rEuLyBCvcw4CFmzv8RepSiAoNgF8tTGJQC validated
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" : {

content/tutorials/use-simple-xrp-payments/send-a-multi-signed-transaction.ja.md

@@ -54,7 +54,7 @@ SlignerListのメンバーの1人のシークレットキーとアドレスを
     >     "SigningPubKey":"",
     >     "Fee":"30000"
     > }'
-    Loading:"/home/mduo13/.config/ripple/rippled.cfg"
+    Loading:"/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" :{
@@ -123,7 +123,7 @@ SlignerListのメンバーの1人のシークレットキーとアドレスを
     >    "TransactionType" :"TrustSet",
     >    "hash" :"A94A6417D1A7AAB059822B894E13D322ED3712F7212CE9257801F96DE6C3F6AE"
     > }'
-    Loading:"/home/mduo13/.config/ripple/rippled.cfg"
+    Loading:"/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" :{
@@ -201,7 +201,7 @@ SlignerListのメンバーの1人のシークレットキーとアドレスを
     >              "TransactionType" :"TrustSet",
     >              "hash" :"BD636194C48FD7A100DE4C972336534C8E710FD008C0F3CF7BC5BF34DAF3C3E6"
     >           }'
-    Loading:"/home/mduo13/.config/ripple/rippled.cfg"
+    Loading:"/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
     	"result":{
@@ -251,7 +251,7 @@ SlignerListのメンバーの1人のシークレットキーとアドレスを
 スタンドアロンモードで`rippled`を実行している場合は、[ledger_acceptメソッド][]を使用してレジャーを手動で閉鎖します。
 
     $ rippled ledger_accept
-    Loading:"/home/mduo13/.config/ripple/rippled.cfg"
+    Loading:"/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" :{
@@ -270,7 +270,7 @@ SlignerListのメンバーの1人のシークレットキーとアドレスを
 スタンドアロンモードでは、サーバーは手動で閉鎖されたレジャーを自動的に`validated`とみなします。
 
     $ rippled tx BD636194C48FD7A100DE4C972336534C8E710FD008C0F3CF7BC5BF34DAF3C3E6
-    Loading:"/home/mduo13/.config/ripple/rippled.cfg"
+    Loading:"/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
     	"result":{

content/tutorials/use-simple-xrp-payments/send-a-multi-signed-transaction.md

@@ -54,7 +54,7 @@ Use the [sign_for method][] with the secret key and address of one of the member
     >     "SigningPubKey": "",
     >     "Fee": "30000"
     > }'
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" : {
@@ -123,7 +123,7 @@ You can collect additional signatures in parallel or in serial:
     >    "TransactionType" : "TrustSet",
     >    "hash" : "A94A6417D1A7AAB059822B894E13D322ED3712F7212CE9257801F96DE6C3F6AE"
     > }'
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" : {
@@ -201,7 +201,7 @@ If you collected the signatures in parallel, you must manually construct a `tx_j
     >              "TransactionType" : "TrustSet",
     >              "hash" : "BD636194C48FD7A100DE4C972336534C8E710FD008C0F3CF7BC5BF34DAF3C3E6"
     >           }'
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
     	"result": {
@@ -251,7 +251,7 @@ If you are using the live network, you can wait 4-7 seconds for the ledger to cl
 If you're running `rippled` in stand-alone mode, use the [ledger_accept method][] to manually close the ledger:
 
     $ rippled ledger_accept
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
        "result" : {
@@ -270,7 +270,7 @@ On the live network, you must also confirm that the `validated` field is set to
 In stand-alone mode, the server automatically considers a ledger to be `validated` if it has been manually closed.
 
     $ rippled tx BD636194C48FD7A100DE4C972336534C8E710FD008C0F3CF7BC5BF34DAF3C3E6
-    Loading: "/home/mduo13/.config/ripple/rippled.cfg"
+    Loading: "/etc/opt/ripple/rippled.cfg"
     Connecting to 127.0.0.1:5005
     {
     	"result": {