Update DAS arguments that were changed in nitro 2.1.0

arbitrum-docs/for-devs/third-party-docs/PARSIQ/parsiq.md

@@ -1,12 +1,11 @@
 ---
-title: "Quickstart: PARSIQ (blockchain data API & SDK)"
-description: "Learn how to use PARSIQ API and SDK to get Arbitrum data"
+title: 'Quickstart: PARSIQ (blockchain data API & SDK)'
+description: 'Learn how to use PARSIQ API and SDK to get Arbitrum data'
 author: Ivan-Ivanitskiy
 sme: Ivan-Ivanitskiy
-sidebar_label: "PARSIQ"
+sidebar_label: 'PARSIQ'
 ---
 
-
 **[<ins>PARSIQ</ins>](https://www.parsiq.net/)** is a reliable, fully customizable blockchain data indexer, helping developers to seamlessly access, process and utilize Web3 data - both raw and custom.
 
 PARSIQ API allows querying blockchain data such as transactions, token transfers, events, internal function calls, blocks, etc.
@@ -19,6 +18,7 @@ to get started.
 ## PARSIQ Tsunami API
 
 PARSIQ Tsunami API is a highly efficient API to fetch raw Web3 data:
+
 - Events, calls, transactions (internal included), transfers, contracts, blocks - you name it. Possibility to use unlimited blockrange makes Tsunami a hard-to-beat solution for realiably getting large amounts of data from the blockchain. CSV Export is available.
 - Get decoded, human readable data right out of the box.
 - Need an up to date feeds of data streamed to you in real time? Give our low latency Real Time Streaming service a try.
@@ -31,11 +31,10 @@ Please check out our [<ins>PARSIQ API Reference</ins>](https://docs.parsiq.net/r
 
 ## PARSIQ SDK
 
-Some more complicated cases where custom data needs to be stored, accumulated, and calculated, cannot be covered by an API. In that cases, use PARSIQ SDK or go for a Custom Data Lake. They allow you to set up data bases and data processing logic to solve your specific use case. 
+Some more complicated cases where custom data needs to be stored, accumulated, and calculated, cannot be covered by an API. In that cases, use PARSIQ SDK or go for a Custom Data Lake. They allow you to set up data bases and data processing logic to solve your specific use case.
 
 :::info SDK Documentation
 
 Please see [<ins>PARSIQ SDK documentation</ins>](https://docs.parsiq.net/reference/your-own-web3-api) for more details.
 
 :::
-

arbitrum-docs/node-running/how-tos/running-a-daserver.mdx

@@ -57,8 +57,8 @@ Options for both committee members and mirrors:
       --rest-port uint                                                                             REST server listening port (default 9877)
 
  # L1 options
-      --data-availability.l1-node-url string                                                       URL for L1 node, only used in standalone daserver; when running as part of a node that node's L1 configuration is used
-      --data-availability.sequencer-inbox-address string                                           L1 address of SequencerInbox contract
+      --data-availability.parent-chain-node-url string                                             URL for parent chain node, only used in standalone daserver; when running as part of a node that node's parent chain configuration is used
+      --data-availability.sequencer-inbox-address string                                           parent chain address of SequencerInbox contract
 
  # Storage options
       --data-availability.local-db-storage.data-dir string                                         directory in which to store the database
@@ -238,7 +238,7 @@ spec:
         - -c
         - |
 		  mkdir -p /home/user/data/badgerdb
-          /usr/local/bin/daserver --data-availability.l1-node-url <YOUR ETHEREUM L1 RPC ENDPOINT>
+          /usr/local/bin/daserver --data-availability.parent-chain-node-url <YOUR ETHEREUM L1 RPC ENDPOINT>
 --enable-rpc --rpc-addr '0.0.0.0' --enable-rest --rest-addr '0.0.0.0' --log-level 3 --data-availability.local-db-storage.enable --data-availability.local-db-storage.data-dir /home/user/data/badgerdb --data-availability.local-db-storage.discard-after-timeout --data-availability.s3-storage.enable --data-availability.s3-storage.access-key "<YOUR ACCESS KEY>" --data-availability.s3-storage.bucket <YOUR BUCKET> --data-availability.s3-storage.region <YOUR REGION> --data-availability.s3-storage.secret-key "<YOUR SECRET KEY>" --data-availability.s3-storage.object-prefix "YOUR OBJECT KEY PREFIX/" --data-availability.s3-storage.discard-after-timeout --data-availability.key.key-dir /home/user/data/keys  --data-availability.local-cache.enable --data-availability.rest-aggregator.enable --data-availability.rest-aggregator.online-url-list "https://nova.arbitrum.io/das-servers" --data-availability.sequencer-inbox-address '0x211e1c4c7f1bf5351ac850ed10fd68cffcf6c21b'
         image: @latestNitroNodeImage@
         imagePullPolicy: Always
@@ -339,7 +339,7 @@ spec:
         - |
 		  mkdir -p /home/user/data/badgerdb
 		  mkdir -p /home/user/data/syncState
-          /usr/local/bin/daserver --data-availability.l1-node-url <YOUR ETHEREUM L1 RPC ENDPOINT>
+          /usr/local/bin/daserver --data-availability.parent-chain-node-url <YOUR ETHEREUM L1 RPC ENDPOINT>
 --enable-rest --rest-addr '0.0.0.0' --log-level 3  --data-availability.local-db-storage.enable --data-availability.local-db-storage.data-dir /home/user/data/badgerdb --data-availability.s3-storage.enable --data-availability.s3-storage.access-key "<YOUR ACCESS KEY>" --data-availability.s3-storage.bucket <YOUR BUCKET> --data-availability.s3-storage.region <YOUR REGION> --data-availability.s3-storage.secret-key "<YOUR SECRET KEY>" --data-availability.s3-storage.object-prefix "YOUR OBJECT KEY PREFIX/" --data-availability.local-cache.enable --data-availability.rest-aggregator.enable --data-availability.rest-aggregator.urls "http://your-committee-member.svc.cluster.local:9877" --data-availability.rest-aggregator.online-url-list "https://nova.arbitrum.io/das-servers" --data-availability.rest-aggregator.sync-to-storage.eager --data-availability.rest-aggregator.sync-to-storage.eager-lower-bound-block 15025611 --data-availability.sequencer-inbox-address '0x211e1c4c7f1bf5351ac850ed10fd68cffcf6c21b' --data-availability.rest-aggregator.sync-to-storage.state-dir /home/user/data/syncState
         image: @latestNitroNodeImage@
         imagePullPolicy: Always
@@ -408,7 +408,7 @@ spec:
         - |
 		  mkdir -p /home/user/data/ipfsRepo
 		  mkdir -p /home/user/data/syncState
-          /usr/local/bin/daserver --data-availability.l1-node-url <YOUR ETHEREUM L1 RPC ENDPOINT> --enable-rest --rest-addr '0.0.0.0' --log-level 3 --data-availability.ipfs-storage.enable --data-availability.ipfs-storage.repo-dir /home/user/data/ipfsRepo --data-availability.rest-aggregator.enable --data-availability.rest-aggregator.urls "http://your-committee-member.svc.cluster.local:9877" --data-availability.rest-aggregator.online-url-list "https://nova.arbitrum.io/das-servers" --data-availability.rest-aggregator.sync-to-storage.eager --data-availability.rest-aggregator.sync-to-storage.eager-lower-bound-block 15025611 --data-availability.sequencer-inbox-address '0x211e1c4c7f1bf5351ac850ed10fd68cffcf6c21b' --data-availability.rest-aggregator.sync-to-storage.state-dir /home/user/data/syncState
+          /usr/local/bin/daserver --data-availability.parent-chain-node-url <YOUR ETHEREUM L1 RPC ENDPOINT> --enable-rest --rest-addr '0.0.0.0' --log-level 3 --data-availability.ipfs-storage.enable --data-availability.ipfs-storage.repo-dir /home/user/data/ipfsRepo --data-availability.rest-aggregator.enable --data-availability.rest-aggregator.urls "http://your-committee-member.svc.cluster.local:9877" --data-availability.rest-aggregator.online-url-list "https://nova.arbitrum.io/das-servers" --data-availability.rest-aggregator.sync-to-storage.eager --data-availability.rest-aggregator.sync-to-storage.eager-lower-bound-block 15025611 --data-availability.sequencer-inbox-address '0x211e1c4c7f1bf5351ac850ed10fd68cffcf6c21b' --data-availability.rest-aggregator.sync-to-storage.state-dir /home/user/data/syncState
         image: @latestNitroNodeImage@
         imagePullPolicy: Always
         resources: