Add missing changes

Fix for W3C validator and RTL layout
Replace some technical words
This commit is contained in:
Saivann 2013-09-20 22:56:08 -04:00
parent 05faca9bfe
commit 32823dc08a

View file

@ -49,7 +49,7 @@ en:
invoice: "Bitcoin addresses to track invoices"
invoicetext: "Bitcoin creates a unique address for each transaction. So if you were to build a payment system associated with an invoice, you simply need to generate and monitor a Bitcoin address for each payment. You should never use the same address for more than one transaction."
security: "Most of the security is on client side"
securitytext: "Most parts of the security are handled by the protocol on the client and Bitcoin network side. Authenticity is verified with digital signatures, and chargebacks are prevented with the block chain. This means no need for PCI compliance, and fraud detection is only required when services or products are delivered instantly."
securitytext: "Most parts of the security are handled by the protocol on the client and Bitcoin network side. Authenticity is verified with digital signatures, and chargebacks are prevented by the Bitcoin network after a short delay. This means no need for PCI compliance, and fraud detection is only required when services or products are delivered instantly."
micro: "Cheap micro payments"
microtext: "Bitcoin offers the lowest payment processing fees for any type of transaction, including micro-payments. This means that it can also be used to design and implement new creative online services that could not exist before only because of financial limitations."
serviceslist: "Visit the <a href=\"https://en.bitcoin.it/wiki/How_to_accept_Bitcoin,_for_small_businesses#Merchant_Services\">merchant services list</a> on the wiki."
@ -141,7 +141,7 @@ en:
disclosuretxt: "If you find a vulnerability related to Bitcoin, non-critical vulnerabilities can be emailed in English to any of the core developers or sent to the private <a href=\"mailto:bitcoin-security@lists.sourceforge.net\">bitcoin-security@lists.sourceforge.net</a> mailing list. An example of a non-critical vulnerability would be an expensive-to-carry-out denial of service attack. Critical vulnerabilities that are too sensitive for unencrypted email should be sent to one or more of the core developers, encrypted with their PGP key(s)."
involve: "Get involved"
involvetxt1: "Bitcoin development is open-source and any developer can contribute to the project. Everything you need is in the <a href=\"https://github.com/bitcoin/bitcoin\">GitHub repository</a>. Please make sure to read and follow the development process described in the README, as well as to provide good quality code and respect all guidelines."
involvetxt2: "Development discussion takes place on GitHub and the <a href=\"http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development\">bitcoin-development</a> mailing list at sourceforge. Less formal development discussion happens on irc.freenode.net #bitcoin-dev (&rarr;<a href=\"#\" onclick=\"freenodeShow(event);\" />web interface</a>; <a href=\"http://bitcoinstats.com\">logs</a>)."
involvetxt2: "Development discussion takes place on GitHub and the <a href=\"http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development\">bitcoin-development</a> mailing list at sourceforge. Less formal development discussion happens on irc.freenode.net #bitcoin-dev (<a href=\"#\" onclick=\"freenodeShow(event);\">web interface</a>, <a href=\"http://bitcoinstats.com\">logs</a>)."
more: "More open-source projects"
moremore: "Show more.."
contributors: "Bitcoin-Qt contributors"
@ -266,7 +266,7 @@ en:
bettercurrencytxt1: "That can happen. For now, Bitcoin remains by far the most popular decentralized virtual currency, but there can be no guarantee that it will retain that position. There is already a set of alternative currencies inspired by Bitcoin. It is however probably correct to assume that significant improvements would be required for a new currency to overtake Bitcoin in terms of established market, even though this remains unpredictable. Bitcoin could also conceivably adopt improvements of a competing currency so long as it doesn't change fundamental parts of the protocol."
transactions: "Transactions"
tenminutes: "Why do I have to wait 10 minutes?"
tenminutestxt1: "Receiving a payment is almost instant with Bitcoin. However, there is a 10 minutes delay on average before the network begins to confirm your transaction by including it in a block and before you can spend the bitcoins you receive. A confirmation means that there is a consensus on the network that the bitcoins you received haven't been sent to anyone else and are considered your property. Once your transaction has been included in one block, it will continue to be buried under every block after it, which will exponentially consolidate this consensus and decrease the risk of a reversed transaction. Every user is free to determine at what point they consider a transaction confirmed, but 6 blocks is often considered to be as safe as waiting 6 months on a credit card transaction."
tenminutestxt1: "Receiving a payment is almost instant with Bitcoin. However, there is a 10 minutes delay on average before the network begins to confirm your transaction by including it in a block and before you can spend the bitcoins you receive. A confirmation means that there is a consensus on the network that the bitcoins you received haven't been sent to anyone else and are considered your property. Once your transaction has been included in one block, it will continue to be buried under every block after it, which will exponentially consolidate this consensus and decrease the risk of a reversed transaction. Every user is free to determine at what point they consider a transaction confirmed, but 6 confirmations is often considered to be as safe as waiting 6 months on a credit card transaction."
fee: "How much will the transaction fee be?"
feetxt1: "Most transactions can be processed without fees, but users are encouraged to pay a small voluntary fee for faster confirmation of their transactions and to remunerate miners. When fees are required, they generally don't exceed a few pennies in value. Your Bitcoin client will usually try to estimate an appropriate fee when required."
feetxt2: "Transaction fees are used as a protection against users sending transactions to overload the network. The precise manner in which fees work is still being developed and will change over time. Because the fee is not related to the amount of bitcoins being sent, it may seem extremely low (0.0005 BTC for a 1,000 BTC transfer) or unfairly high (0.004 BTC for a 0.02 BTC payment). The fee is defined by attributes such as data in transaction and transaction recurrence. For example, if you are receiving a large number of tiny amounts, then fees for sending will be higher. Such payments are comparable to paying a restaurant bill using only pennies. Spending small fractions of your bitcoins rapidly may also require a fee. If your activity follows the pattern of conventional transactions, the fees should remain very low."