Merge pull request #2369 from plowsof/duplicated

chore: remove repetetive words

_i18n/en/resources/user-guides/importing_blockchain.md

@@ -56,4 +56,4 @@ For example I would type :
 
 ### Step 7
 
-After the the blockchain has finished syncing up you can open your Monero wallet normally. Your downloaded blockchain.raw can be deleted.
+After the blockchain has finished syncing up you can open your Monero wallet normally. Your downloaded blockchain.raw can be deleted.

_i18n/en/resources/user-guides/multisig-messaging-system.md

@@ -821,7 +821,7 @@ The normal MMS wallet syncing process assumes that all signers are cooperative a
 
 However, with *M* being smaller than *N* in configurations like 2/3 multisig you can successfully sync with only (number of required signers minus 1) sync messages. `mms next` will tell you when you have reached this lower threshold and give a hint how to override and go ahead early: Use `mms next sync`.
 
-If later you receive more sync data messages nevertheless just delete them with `mms delete`: They are unneeded, unprocessable for you and worst case will mess up the the next sync round.
+If later you receive more sync data messages nevertheless just delete them with `mms delete`: They are unneeded, unprocessable for you and worst case will mess up the next sync round.
 
 Usually if you initiate sync the MMS will create messages to *all* other signers. If you want to prevent that to make it as hard as possible for other signers to transact further, make sure to set `auto-send` to false, answer "No" when first being asked to send, and manually delete any unwanted messages before sending the rest out with `mms send`.
 

_posts/2014-06-18-monero-missive-for-the-week-of-2014-06-16.md

@@ -24,4 +24,4 @@ This feature requires more testing, and is NOT in the main code base yet. If you
 
 4. We have had a lot of people asking about the progress of the GUI wallet. We'd like to reiterate that there are a great number of core and fundamental things that need to be worked on *before* we can get lots and lots of users flocking in. Some of the core necessities that we're working on at breakneck pace are: QoS to reduce the bandwidth demand on full nodes (as everyone will be running a full node at this stage anyway), segregation of wallet functions in order to create a far more robust system for exchanges and merchants to use, [Gitian-based builds](http://gitian.org) for everyone's safety and to ensure binaries are safe (safer, really), moving blockchain storage to an embedded database, fixing the now-infamous "ABSTRACT_SERVER_SEND_QUE_MAX_COUNT" (in big red letters!) error that is quite harmless but everyone freaks out about, and so on.
 
-   These are issues at Monero's core that we're working on, and we need to have these in place and fixed before a GUI wallet is widely dispersed, otherwise there will be massive resource constraints placed on user's systems. We're not here to win a race against other cryptocurrencies. We're here to to continue to push out great features and stable and reliable code, in a way that will make sure Monero is around for decades and not just a flash-in-the-pan.
+   These are issues at Monero's core that we're working on, and we need to have these in place and fixed before a GUI wallet is widely dispersed, otherwise there will be massive resource constraints placed on user's systems. We're not here to win a race against other cryptocurrencies. We're here to continue to push out great features and stable and reliable code, in a way that will make sure Monero is around for decades and not just a flash-in-the-pan.

_posts/2015-03-02-monero-missive-for-the-week-of-2015-03-02.md

@@ -119,7 +119,7 @@ You know, we use Google Maps, he uses MMAP!
 
 Ok, so that really should give all our listeners an indication as to what the current state of the database is, the painpoints we've faced and have had to overcome, and what we're going to be doing in future...not only to make Monero run on multiple platforms, but to make it run smoothly and efficiently on the smallest of devices.
 
-So that's the database, I think that's the bulk of what we wanted to chat about about the database, unless there's anything else you'd like to add.
+So that's the database, I think that's the bulk of what we wanted to chat about the database, unless there's anything else you'd like to add.
 
 #### Gingeropolous
 

_posts/2015-09-14-monero-missive-for-the-week-of-2015-09-14.md

@@ -279,7 +279,7 @@ Yea, I'm sorry
 
 #### Riccardo
 
-But, I think the other thing that's come out of this, that's been quite cool is that rznag's written a little test system in Python that uses the the Tippero Python Library, and that's great for system automators, or merchants, or developers that are using Monero. The whole ecosystem's starting to build up now, where there are a lot of libraries with tools to test them, and so, I think the more that stuff happens over time, the easier it's going to be for integrators to just like say, “ok, I'm going to take this library and use it”, rather than sitting in #Monero-dev IRC channel and asking for help.
+But, I think the other thing that's come out of this, that's been quite cool is that rznag's written a little test system in Python that uses the Tippero Python Library, and that's great for system automators, or merchants, or developers that are using Monero. The whole ecosystem's starting to build up now, where there are a lot of libraries with tools to test them, and so, I think the more that stuff happens over time, the easier it's going to be for integrators to just like say, “ok, I'm going to take this library and use it”, rather than sitting in #Monero-dev IRC channel and asking for help.
 
 #### Gingeropolous
 

_posts/2016-02-10-monero-missive-2015-year-in-review.md

@@ -72,7 +72,7 @@ Some [highlights of the FFS over the year](https://forum.getmonero.org/9/work-in
 
 - [tewinget's Documentation and Cleanup of Source Code](https://forum.getmonero.org/9/work-in-progress/2373/documentation-and-cleanup-of-source-code): raised 3600 XMR in 23 contributions; completed 3/4 milestones.
 - [moneromoo's initial fundraiser for 6 months of work](https://forum.getmonero.org/22/completed-tasks/334/fund-a-developer-moneromoo-will-work-part-time-on-monero-for-260-hours-over-approx-6-months): raised over its target of 7800 XMR in 45 contributions; completed all 6 milestones.
-- [moneromoo's second fundraiser for for about 10 additional months of work](https://forum.getmonero.org/9/work-in-progress/2410/a-continuation-for-all-purpose-programming-of-what-needs-to-get-done-in-monero): raised 18000 XMR in 21 contributions; completed 3/10 milestones thus far.
+- [moneromoo's second fundraiser for about 10 additional months of work](https://forum.getmonero.org/9/work-in-progress/2410/a-continuation-for-all-purpose-programming-of-what-needs-to-get-done-in-monero): raised 18000 XMR in 21 contributions; completed 3/10 milestones thus far.
 - [Shen Noether's translation of some of the website content into Chinese](https://forum.getmonero.org/9/work-in-progress/329/translation-of-content-on-getmonero-org-into-chinese): raised 950 XMR from a target of 600 XMR in 9 contributions; completed its milestone.
 - [Shen Noether's fundraiser to complete the C++ implementation of RingCT](https://forum.getmonero.org/9/work-in-progress/2450/ring-ct-c-crypto): raised 3150 XMR in 13 contributions; has very nearly reached completion of all 7 of its milestones.
 - [Wolf0's very efficient AMD miner](https://forum.getmonero.org/9/work-in-progress/2400/open-source-amd-miner-by-wolf0): raised 7750 XMR in 20 contributions; completed 6/7 milestones.

_posts/2016-12-22-monero-core-gui-beta-released.md

@@ -14,7 +14,7 @@ Download links are at the bottom of this post, and please take note of the known
 
 ### Known Issues
 
-- Due to several important updates, 0.10.1 wallet binaries will not work with with wallets created by the GUI. Please use the binaries included in the package instead. Note: you can definitely use the 0.10.1 daemon:)
+- Due to several important updates, 0.10.1 wallet binaries will not work with wallets created by the GUI. Please use the binaries included in the package instead. Note: you can definitely use the 0.10.1 daemon:)
 - If you have been testing earlier builds you may have to delete your configs. There is [a guide describing how to do this on this StackExchange post](http://monero.stackexchange.com/questions/2866/where-are-the-monero-core-configuration-parameters-stored/2870#2870).
 - Older computers may have an issue with the QT renderer, and will either crash or display a white / black window. You can change the rendering mode [as described on this StackExchange post](http://monero.stackexchange.com/questions/2928/how-to-change-the-monero-core-rendering-mode-for-older-computers/2929#2929).
 

_posts/2018-10-11-monero-0.13.0-released.md

@@ -167,7 +167,7 @@ Some highlights of this major release are:
 - Fix output shuffling for multisig
 - Fix race adding the same tx twice to the txpool
 - fix configuring version.cpp without git
-- Add warnings about inaccurate balances to to watch-only wallet
+- Add warnings about inaccurate balances to watch-only wallet
 - New unit tests
 - Many more smaller fixes, speedups, improvements and other tweaks
 

_posts/2019-06-04-Long-Payment-ID-Deprecation.md

@@ -36,7 +36,7 @@ In sum, payment IDs have serveral salient drawbacks and will therefore
 be phased out. Services are recommended to upgrade to subaddresses as
 soon as possible. Subaddresses essentially function similar to Bitcoin
 HD wallets and should thus be relatively straightforward to implement.
-Furthermore, subaddresses are managable from a resource point point of
+Furthermore, subaddresses are managable from a resource point of
 view.
 
 Yours sincerely,

legal/index.md

@@ -65,7 +65,7 @@ As a convenience to Users, the The Monero Project website and services may provi
 
 ### Password Protected Areas
 
-Some areas of the The Monero Project site ("Password Protected Areas"), primarily the Monero forum, are password protected and available only to Users who are registered on the Monero forum. Registration requires Users to fully complete the account registration process. The Monero Project reserves the right to deny or revoke registration or access to Password Protected Areas for any User. The Monero Project takes reasonable measures to ensure the security of the Password Protected Areas but cannot guarantee the absolute security of information or communications in such Password Protected Areas. Users are responsible for maintaining the security of the password they set and must notify us if they believe that the security of their password or account has been breached or subject to unauthorized use. Additional account security is available through the use of GPG authentication, and all users of any Password Protected Areas are encouraged to take advantage of this layer of protection. The Monero Project will not be liable for any loss or liability incurred as a result of an unauthorized person using a User's password.
+Some areas of The Monero Project site ("Password Protected Areas"), primarily the Monero forum, are password protected and available only to Users who are registered on the Monero forum. Registration requires Users to fully complete the account registration process. The Monero Project reserves the right to deny or revoke registration or access to Password Protected Areas for any User. The Monero Project takes reasonable measures to ensure the security of the Password Protected Areas but cannot guarantee the absolute security of information or communications in such Password Protected Areas. Users are responsible for maintaining the security of the password they set and must notify us if they believe that the security of their password or account has been breached or subject to unauthorized use. Additional account security is available through the use of GPG authentication, and all users of any Password Protected Areas are encouraged to take advantage of this layer of protection. The Monero Project will not be liable for any loss or liability incurred as a result of an unauthorized person using a User's password.
 
 ### Prohibited Conduct
 
@@ -102,7 +102,7 @@ THE MONERO PROJECT DISCLAIMS ALL WARRANTIES, REPRESENTATIONS AND CONDITIONS OF A
 
 ### EXCLUSION OF CONSEQUENTIAL DAMAGES
 
-IN NO EVENT WILL THE MONERO PROJECT BE LIABLE FOR ANY INCIDENTAL, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR INDIRECT DAMAGES ARISING OUT OF THE USE OF OR INABILITY TO USE THIS WEBSITE OR ANY OF ITS SERVICES OR CONTENT, OR LOSS OF DATA, EVEN IF THE MONERO PROJECT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, PRODUCT LIABILITY, STRICT LIABILITY OR OTHERWISE.
+IN NO EVENT WILL THE MONERO PROJECT BE LIABLE FOR ANY INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR INDIRECT DAMAGES ARISING OUT OF THE USE OF OR INABILITY TO USE THIS WEBSITE OR ANY OF ITS SERVICES OR CONTENT, OR LOSS OF DATA, EVEN IF THE MONERO PROJECT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, PRODUCT LIABILITY, STRICT LIABILITY OR OTHERWISE.
 
 ### EXCLUSION OF LIMITATIONS AND DISCLAIMERS