proofed, added hacktoberfest image

content/news/226-sept-dev-2019.md

@@ -9,40 +9,12 @@ Welcome to the September 2019 LBRY Development update! In this post we’ll show
 
 To read previous updates, please visit our [Development and Community Update archive](https://lbry.com/news/category/community-update).
 
-If you want to see a condensed view of what we have completed recently and what’s planned for LBRY, check out our [Roadmap](https://lbry.io/roadmap).
+If you want to see a condensed view of what we've completed recently and what’s planned for LBRY, check out our [Roadmap](https://lbry.io/roadmap).
 
-First off, let’s start with some GitHub stats across all our repos (some of which are internal only to LBRY) since our last update about 31 days ago:  
+Let’s start with some GitHub stats across all our repos (some of which are internal only to LBRY) since our last update about 31 days ago: 
 38 repos were updated. 550 issues were created, 160 were closed. 29 PRs were merged. 30 GitHub users outside of LBRY made code contributions, including some early ones for [Hacktoberfest](#hacktoberfest): 
-- [AlessandroSpallina](https://github.com/AlessandroSpallina)
-- [amaljose02](https://github.com/amaljose02)
-- [Bharat123rox](https://github.com/Bharat123rox)
-- [Borewit](https://github.com/Borewit)
-- [ceoger](https://github.com/ceoger)
-- [Coolguy3289](https://github.com/Coolguy3289)
-- [dangarthwaite](https://github.com/dangarthwaite)
-- [danielcaldas](https://github.com/danielcaldas)
-- [eggplantbren](https://github.com/eggplantbren)
-- [felhe](https://github.com/felhe)
-- [hugovk](https://github.com/hugovk)
-- [ICTman1076](https://github.com/ICTman1076)
-- [JakeVdub](https://github.com/JakeVdub)
-- [jamesgeorge007](https://github.com/jamesgeorge007)
-- [kodxana](https://github.com/kodxana)
-- [ksami](https://github.com/ksami)
-- [mirgee](https://github.com/mirgee)
-- [OrginalS](https://github.com/OrginalS)
-- [osilkin98](https://github.com/osilkin98)
-- [pankajpatel](https://github.com/pankajpatel)
-- [Parikshit-Hooda](https://github.com/Parikshit-Hooda)
-- [ProfessorDey](https://github.com/ProfessorDey)
-- [pranabs1ngh](https://github.com/pranabs1ngh)
-- [priyapande](https://github.com/priyapande)
-- [rishav142k](https://github.com/rishav142k)
-- [StrikerRUS](https://github.com/StrikerRUS)
-- [Taminoful](https://github.com/Taminoful)
-- [utkarshiam](https://github.com/utkarshiam)
-- [ykris45](https://github.com/ykris45)
-- [zxawry](https://github.com/zxawry)
+
+[AlessandroSpallina](https://github.com/AlessandroSpallina), [amaljose02](https://github.com/amaljose02), [Bharat123rox](https://github.com/Bharat123rox), [Borewit](https://github.com/Borewit), [ceoger](https://github.com/ceoger), [Coolguy3289](https://github.com/Coolguy3289), [dangarthwaite](https://github.com/dangarthwaite), [danielcaldas](https://github.com/danielcaldas), [eggplantbren](https://github.com/eggplantbren), [felhe](https://github.com/felhe), [hugovk](https://github.com/hugovk), [ICTman1076](https://github.com/ICTman1076), [JakeVdub](https://github.com/JakeVdub), [jamesgeorge007](https://github.com/jamesgeorge007), [kodxana](https://github.com/kodxana), [ksami](https://github.com/ksami), [mirgee](https://github.com/mirgee), [OrginalS](https://github.com/OrginalS), [osilkin98](https://github.com/osilkin98), [pankajpatel](https://github.com/pankajpatel), [Parikshit-Hooda](https://github.com/Parikshit-Hooda), [ProfessorDey](https://github.com/ProfessorDey), [pranabs1ngh](https://github.com/pranabs1ngh), [priyapande](https://github.com/priyapande), [rishav142k](https://github.com/rishav142k), [StrikerRUS](https://github.com/StrikerRUS), [Taminoful](https://github.com/Taminoful), [utkarshiam](https://github.com/utkarshiam), [ykris45](https://github.com/ykris45), [zxawry](https://github.com/zxawry)
 
 Thanks to everyone who took time out of their busy days to help LBRY out!
  
@@ -58,22 +30,26 @@ Thanks to everyone who took time out of their busy days to help LBRY out!
 * [2019 Roadmap Progress](#roadmap)
 
 ### Hacktoberfest at LBRY! {#hacktoberfest}
-If you are a developer who is interested in LBRY, there's never been a better time to start contributing! It's October, which means Digital Ocean is running their Hacktoberfest promotion of open source projects and LBRY is all in! As with all contributions to LBRY, we offer generous [appreciation](/faq/appreciation) in LBC on top of this month's special prizes. There’s also a [developer program](https://lbry.tech/developer-program) to get you started with some LBRY credits.
+If you are a developer who is interested in LBRY, there's never been a better time to start contributing! It's October, which means Digital Ocean is running their Hacktoberfest promotion of open source projects, and LBRY is all in! As with all contributions to LBRY, we offer generous [appreciation](/faq/appreciation) in LBC on top of this month's special prizes, including t-shirts and stickers. There’s also a [developer program](https://lbry.tech/developer-program) to get you started with some LBRY credits.
 
-Check out our [blog post](/news/hacktoberfest-2019) for all the details or dive right in on GitHub by checking out Hacktoberfest tagged issues on popular repositories such as  
-[lbry-desktop](https://github.com/lbryio/lbry-desktop/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)
-[lbry-android](https://github.com/lbryio/lbry-android/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)
-[lbry-sdk](https://github.com/lbryio/lbry-sdk/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest). 
-[lbrycrd](https://github.com/lbryio/lbrycrd/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)
+Check out our [blog post](/news/hacktoberfest-2019) for all the details including live help sessions, or dive right in on GitHub and check out Hacktoberfest tagged issues on popular repositories such as:  
+- [lbry-desktop](https://github.com/lbryio/lbry-desktop/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)
+- [lbry-android](https://github.com/lbryio/lbry-android/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)
+- [lbry-sdk](https://github.com/lbryio/lbry-sdk/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest). 
+- [lbrycrd](https://github.com/lbryio/lbrycrd/issues?q=is%3Aopen+is%3Aissue+label%3Ahacktoberfest)
 
 If you need help getting started with any of the repos, make sure to check out the READMEs in each or [these developer setup videos](https://lbry.tech/resources/setup-videos). There’s also a [glossary](https://lbry.tech/glossary) if you need help getting up to speed on Blockchain/LBRY lingo. 
 
+![Hacktoberfest](https://spee.ch/@lbrynews:0/hacktoberfest-lbry.png)
+
 ### Desktop App {#summary-desktop}
-Since our last development update, the app team shipped our next named release, [0.36.0](https://github.com/lbryio/lbry-desktop/releases/tag/v0.36.0), under codename [Galileo](https://lbry.com/news/galileo). Galileo is a huge release in terms of new features, many of them geared towards [YouTube Sync](#yt-sync) partners and power users, but it also includes a [new sign-in](#sign-in) experience and our first release of [wallet syncing on Desktop](#wallet-sync). 
+Since our last development update, the app team shipped our next named release, [0.36.0](https://github.com/lbryio/lbry-desktop/releases/tag/v0.36.0), under codename [Galileo](https://lbry.com/news/galileo). 
+
+Galileo is a huge release in terms of new features, many of them geared towards [YouTube Sync](#yt-sync) partners and power users, but it also includes a [new sign-in](#sign-in) experience and our first release of [wallet syncing on Desktop](#wallet-sync). 
 
 Other new features in Galileo and since our last update include:
-- A Channels page that lists a user’s created channels, including any that are eligible to be transferred as from YouTube sync.
-- Subscriber counts on Channel pages and view counts on content for all users
+- A Channels page that lists a user’s created channels, including any that are eligible to be transferred as from YouTube sync
+- Subscriber counts on Channel pages and view counts on content for all users.
 - More detailed balance information on the Wallet page - includes total locked tips and LBC staked in publishes/channels/supports.
 - Pagination support on Publishes/Downloads/Transaction history - helps improve power user app performance.
 - Search content within a channel on the channel page.
@@ -84,7 +60,7 @@ Other new features in Galileo and since our last update include:
 - Better internationalization support, more languages can be added easily now.
 
 Since our last named release, we’ve squashed a few bugs, including:
-- Autoplay next not working.
+- Autoplay-next not working.
 - Ensuring views are counted for rewards purposes.
 - Not being able to delete published content that wasn’t downloaded.
 - Showing duration for audio files.
@@ -94,11 +70,11 @@ Since our last named release, we’ve squashed a few bugs, including:
 
 #### YouTube Sync Claiming and Transfers {#yt-sync}
 
-Galileo enables a long awaited and necessary feature to close the loop in our [YouTube Sync Partner Program](https://lbry.com/youtube) - the claiming and transfer process that allows creators to get full control of their channels and content. LBRY will only retain access (using a signing key) to publish new items into the channel and can no longer edit any content or the channel metadata itself. Learn more about how this process works overall on our updated [YouTube Sync FAQ](/faq/youtube).
+Galileo enables a long-awaited and necessary feature to close the loop in our [YouTube Sync Partner Program](https://lbry.com/youtube). This is the claiming and transfer process allowing creators to take full control of their channels and content. LBRY will only retain access (using a signing key) to publish new items into the channel and can no longer edit any content or the channel metadata itself. Learn more about how this process works on our updated [YouTube Sync FAQ](/faq/youtube).
 
-YouTubers will be able to initiate this while signing into LBRY on Desktop (web support coming soon) or accessing their Channels page. This transfer process also supports those who have multiple channels - they are all done with a single click. Once a user clicks **Claim Channel**, their channel identity is imported into their wallet which means it be used immediately to comment/publish new content and their content transfer is queued up. 
+YouTubers can initiate this while signing into LBRY on Desktop (web support coming soon) or accessing their Channels page. This transfer process also supports those who have multiple channels - they are all done with a single click. Once a user clicks **Claim Channel**, their channel identity is imported into their wallet which allows it can be used immediately to comment/publish new content and their content transfer is queued up. 
 
-The transfer process kicks off automatically on our end and progress is shown to the user. The Publishes section of the app will start filling up with their claims as they are updated from our wallets to the users’. Once complete, the pending state will disappear and the channel will be shown just as if it were created by the user themselves. Any tips that the creator received will be sent to their channel as a lump sum, that can be easily claimed or kept to support their discovery on the platform. 
+The transfer process kicks off automatically on our end and progress is shown to the user. The Publishes section of the app will start filling up with their claims as they are updated from our wallet to the user's. Once complete, the pending state  disappears and the channel will be shown as if it were created by the user themself. Any tips that the creator received will be sent to their channel as a lump sum that can be claimed or kept to support their discovery on the platform. 
 
 ![transfer](https://spee.ch/2/sync-faq-2.png)
 
@@ -141,12 +117,14 @@ The main features and bug fixes include:
 - Automatic retrying of failed resolve requests to improve overall experience. 
 - Potentially fix some edge cases that cause memory leaks
 
-A main portion of ongoing work has been to improve support of multi-account scenarios within a wallet, which will allow us to expand wallet syncing to all our users, even those that have multiple existing installations. This also includes wallet wide encryption/decryption methods so that we can sync up accounts without having to worry about tracking different passwords. We also think we tracked down the source of some memory leaks experienced by power users hosting lots of content, so we’ll continue to monitor in the next few weeks to see if they are resolved. We’ve also tackled an issue recently which prevented users on some mobile networks from being able to access content - this should be out in a release on Android mid October and improve overall reliability. 
+A main portion of ongoing work has been to improve support of multi-account scenarios within a wallet, which will allow us to expand wallet syncing to all our users, even those that have multiple existing installations. This also includes wallet wide encryption/decryption methods so that we can sync up accounts without having to worry about tracking different passwords. 
+
+We also think we tracked down the source of some memory leaks experienced by power users hosting lots of content, and we’ll continue to monitor in the next few weeks to see if they are resolved. We’ve also tackled an issue preventing users on some mobile networks from being able to access content. This should be released on Android mid-October and improve overall reliability. 
 
 #### SDK Next Steps
-After clearing out the cross account syncing issues, the team will be focusing on a few new items:
+After clearing out the cross-account syncing issues, the team will focus on a few new items:
 
-- Bridging the gap for purchased content on LBRY. Today, there’s no metadata saved with these purchase transactions so users can’t tell which pieces of content the purchases were for without digging into address level information. We’ll begin saving this in a special transaction so it can be retrieved as part of the transaction history.
+- Bridging the gap for purchased content on LBRY. Today, there’s no metadata saved with these purchase transactions and users can’t tell which pieces of content the purchases were for without digging into address level information. We’ll begin saving this in a special transaction so it can be retrieved as part of the transaction history.
 - Improving performance wallet related API calls like transaction list / claim list. This is required for power users / large content creators to have a smooth app experience. 
 - Supporting the latest Blockchain upgrade changes, including wallet server changes that may be needed and new metadata for support transactions. 
 - Handling of errors in the SDK through the use of error codes.
@@ -158,13 +136,13 @@ Since our last update, the blockchain team released [our next big upgrade](https
 - Metadata for support type transactions
 - SegWit support. This will allow Lightning Network for content and data payments down the road
 
-Support metadata will enable us to expand the support/tipping feature of LBRY, which currently only allows simple LBC transactions to occur, to include additional metadata that can be used for signing the supports to prove channel ownership and enabling use cases like commenting, rating, and subscriptions on chain. Signing of supports will finally give us the ability to link a channel back to a tip transaction, so publishers can see and verify who sent LBC (or even a support). On-chain subscriptions also help further decentralize data you can only find on our API currently, and enable a Patreon-like system where creators can release content that’s accessible only by their supportor’s or at various support/tip levels.
+Support metadata will enable us to expand the support/tipping feature of LBRY, which currently only allows simple LBC transactions to occur, to include additional metadata that can be used for signing the supports to prove channel ownership and enabling use cases like commenting, rating, and subscriptions on-chain. Signing of supports will finally give us the ability to link a channel back to a tip transaction, so publishers can see and verify who sent LBC (or even a support). On-chain subscriptions also help further decentralize data you can only find on our API currently, and enable a Patreon-like system where creators can release content that’s accessible only by their supporters or at various support/tip levels.
 
-You can check out our [blog post for detailed information about this release](https://lbry.com/news/hf1910). LBRY has already notified all those on the upgrade mailing list and will continue to reach out to mining pools, exchanges, and other service operators to ensure they upgrade in time.
+You can check out our [blog post for detailed information about this release](https://lbry.com/news/hf1910). LBRY has already notified everyone on the upgrade mailing list and will continue to reach out to mining pools, exchanges, and other service operators to ensure they upgrade in time.
 
 ### LBRY.tv {#web}
 
-On the backend, we’ve successfully migrated our accounts based model to a wallet ID one, which will allow for a better cross platform experience for our users. This included converting all accounts to separate wallets, importing any channels that may have been created, and loading of user wallets on startup. The wallet based model will also allow us to scale LBRY.tv more efficiently as we can choose what wallets are loaded on which SDK instance supporting the front end. We are in the process of finishing up wallet syncing, but we’ve run into a snag with preference syncing that will require some SDK changes. This should all be cleaned up in a few days, and we’ll be ready for additional testing of the sign in and syncing process. 
+On the backend, we’ve successfully migrated our accounts-based model to a wallet-ID one, which will allow for a better cross platform experience for our users. This included converting all accounts to separate wallets, importing any channels that may have been created, and loading of user wallets on startup. The wallet based model will also allow us to scale LBRY.tv more efficiently as we can choose what wallets are loaded on which SDK instance supporting the front end. We are in the process of finishing up wallet syncing, but we’ve run into a snag with preference syncing that will require some SDK changes. This should all be cleaned up in a few days, and we’ll be ready for additional testing of the sign in and syncing process. 
 
 Eager to give lbry.tv a try now? Head over to [https://beta.lbry.tv](https://beta.lbry.tv) and sign up for an account.