Browse Source

fix: replace quotation marks

feat/faucet
Alexander Graebe 4 years ago
parent
commit
bb8d868409
  1. 2
      src/pages/ecosystem/address-confirmation.md
  2. 2
      src/pages/ecosystem/overview.md
  3. 2
      src/pages/understand-stacks/integrate-stacking-delegation.md
  4. 2
      src/pages/understand-stacks/integrate-stacking.md
  5. 2
      src/pages/understand-stacks/overview.md
  6. 2
      src/pages/understand-stacks/stacking.md

2
src/pages/ecosystem/address-confirmation.md

@ -17,5 +17,5 @@ Make sure to store your hardware wallet's seed phrase (sometimes referred to as
## For Multi-Sig Wallets:
If you used a multi-signature wallet (for advanced users), you will need to re-enter your public keys to check your address (by clicking “Create Multi-signature Wallet”).
If you used a multi-signature wallet (for advanced users), you will need to re-enter your public keys to check your address (by clicking "Create Multi-signature Wallet").
The order that you enter the public keys into the multi-sig wallet is important. If you do not remember the order in which you entered your public keys, please contact hello@StacksToken.com.

2
src/pages/ecosystem/overview.md

@ -68,4 +68,4 @@ are used to register digital assets on the network. The Stacks blockchain v2
will support general-purpose smart contracts written in a non-Turing-complete
language currently under development.
~> This communication contains forward-looking statements that are based on our beliefs and assumptions and on information currently available to us. In some cases, you can identify forward-looking statements by the following words: “will,” “expect,” “would,” “intend,” “believe,” or other comparable terminology. Forward-looking statements in this document include, but are not limited to, statements about our plans for developing the platform and future utility for the Stacks Token, our Clarity smart contracting language, and potential mining operations. These statements involve risks, uncertainties, assumptions and other factors that may cause actual results or performance to be materially different. More information on the factors, risks and uncertainties that could cause or contribute to such differences is included in our filings with the SEC, including in the “Risk Factors” and “Management’s Discussion & Analysis” sections of our offering statement on Form 1-A. We cannot assure you that the forward-looking statements will prove to be accurate. These forward-looking statements speak only as of the date hereof. We disclaim any obligation to update these forward-looking statements.
~> This communication contains forward-looking statements that are based on our beliefs and assumptions and on information currently available to us. In some cases, you can identify forward-looking statements by the following words: "will," "expect," "would," "intend," "believe," or other comparable terminology. Forward-looking statements in this document include, but are not limited to, statements about our plans for developing the platform and future utility for the Stacks Token, our Clarity smart contracting language, and potential mining operations. These statements involve risks, uncertainties, assumptions and other factors that may cause actual results or performance to be materially different. More information on the factors, risks and uncertainties that could cause or contribute to such differences is included in our filings with the SEC, including in the "Risk Factors" and "Management’s Discussion & Analysis" sections of our offering statement on Form 1-A. We cannot assure you that the forward-looking statements will prove to be accurate. These forward-looking statements speak only as of the date hereof. We disclaim any obligation to update these forward-looking statements.

2
src/pages/understand-stacks/integrate-stacking-delegation.md

@ -117,7 +117,7 @@ const cycles = 3;
const delegatorPrivateKey = 'd48f215481c16cbe6426f8e557df9b78895661971d71735126545abddcd5377001';
// the BTC address for reward payouts; either to the delegator or to the BTC address set by the account holder
// must start with "1" or "3". Native Segwit (starts with “bc1”) is not supported
// must start with "1" or "3". Native Segwit (starts with "bc1") is not supported
const delegatorBtcAddress = 'msiYwJCvXEzjgq6hDwD9ueBka6MTfN962Z';
// if you call this method multiple times in the same block, you need to increase the nonce manually

2
src/pages/understand-stacks/integrate-stacking.md

@ -181,7 +181,7 @@ With this input, and the data from previous steps, we can determine the eligibil
```js
// user supplied parameters
// BTC address must start with "1" or "3". Native Segwit (starts with “bc1”) is not supported
// BTC address must start with "1" or "3". Native Segwit (starts with "bc1") is not supported
let btcAddress = '1Xik14zRm29UsyS6DjhYg4iZeZqsDa8D3';
let numberOfCycles = 3;

2
src/pages/understand-stacks/overview.md

@ -25,7 +25,7 @@ PoX is a consensus algorithm between two blockchains. It uses an established blo
PoX connects to Bitcoin with a 1:1 block ratio, meaning anything that happens on the Stacks blockchain can be verified on the Bitcoin Blockchain.
Instead of burning electricity on proof of work, PoX reuses already minted bitcoins as “proof of computation” and
Instead of burning electricity on proof of work, PoX reuses already minted bitcoins as "proof of computation" and
miners represent their cost of mining in bitcoins directly.
[@page-reference | inline]

2
src/pages/understand-stacks/stacking.md

@ -101,7 +101,7 @@ Check out the [Stacking contract reference](/references/stacking-contract) to se
## Bitcoin address
!> You must provide a BTC address in one of two formats: [Legacy (P2PKH)](https://en.bitcoin.it/wiki/Transaction#Pay-to-PubkeyHash), which starts with "1". Or, [Segregated Witness / Segwit (P2SH)](https://en.bitcoin.it/wiki/Pay_to_script_hash), which starts with "3". The "Native Segwit" format (which starts with “bc1”), for example, is not supported.
!> You must provide a BTC address in one of two formats: [Legacy (P2PKH)](https://en.bitcoin.it/wiki/Transaction#Pay-to-PubkeyHash), which starts with "1". Or, [Segregated Witness / Segwit (P2SH)](https://en.bitcoin.it/wiki/Pay_to_script_hash), which starts with "3". The "Native Segwit" format (which starts with "bc1"), for example, is not supported.
The Stacking contract needs a special format for the bitcoin address (the reward address). This is required in order to ensure that miners will be able to correctly construct the bitcoin transaction containing the reward address.

Loading…
Cancel
Save