Redesign

.gitmodules

@@ -0,0 +1,6 @@
+[submodule "web/components"]
+	path = web/components
+	url = https://github.com/lbryio/components
+[submodule "web/scss/color"]
+	path = web/scss/color
+	url = https://github.com/lbryio/color

INSTALL.md

@@ -8,7 +8,7 @@ To run this project, you'll need to have either PHP7 or Docker installed, and be
 
 - Install [PHP7](http://php.net/downloads.php)
 - Possibly install additional PHP extensions: `curl`, `xml`, `mbstring`, `dom`
-- Checkout the project. Be sure to update submodules (`git submodule update --init`).
+- Checkout the project. Be sure to install/update submodules (`git submodule update --recursive --remote`).
 - Run `./dev.sh` from the project root
 - Access [localhost:8000](http://localhost:8000) in your browser
 

README.md

@@ -1,7 +1,7 @@
 # lbry.io
 
 [![MIT licensed](https://img.shields.io/dub/l/vibe-d.svg?style=flat)](https://github.com/lbryio/lbry.io/blob/master/LICENSE)
-[![chat on Discord](https://img.shields.io/discord/362322208485277697.svg?logo=discord)](https://chat.lbry.io) 
+[![chat on Discord](https://img.shields.io/discord/362322208485277697.svg?logo=discord)](https://chat.lbry.io)
 
 The [lbry.io](https://lbry.io) website. This website uses barebones PHP along with Javascript and SCSS.
 
@@ -15,11 +15,11 @@ Please see [INSTALL](INSTALL.md) for comprehensive, easy-to-follow instructions
 
 Unless you are planning to contribute to the lbry.io website, this project serves little independent purpose.
 
-To access a local copy of lbry.io, follow [INSTALL](INSTALL.md) and then access `localhost:8000` in your browser. This will allow you to make changes to the website, test locally and then submit pull requests. 
+To access a local copy of lbry.io, follow [INSTALL](INSTALL.md) and then access `localhost:8000` in your browser. This will allow you to make changes to the website, test locally and then submit pull requests.
 
 ## Running from Source
 
-Please see [INSTALL](INSTALL.md) for details on how to run from source. 
+Please see [INSTALL](INSTALL.md) for details on how to run from source.
 
 ## License
 
@@ -43,6 +43,6 @@ The primary contact for this project is [Jeremy Kauffman](https://github.com/kau
 - [Discord Chat](https://chat.lbry.io) - A chat room for the LBRYians
 - [Email us](mailto:hello@lbry.io) - LBRY Support email
 - [Twitter](https://twitter.com/@lbryio) - LBRY Twitter page
-- [Facebook](https://www.facebook.com/lbryio/) - LBRY Facebook page
+- [Facebook](https://www.facebook.com/lbryio) - LBRY Facebook page
 - [Reddit](https://reddit.com/r/lbry) - LBRY Reddit page
 - [Telegram](https://t.me/lbryofficial) - Telegram group

composer.json

@@ -5,7 +5,7 @@
     "ext-curl": "*",
     "ext-mbstring": "*",
     "ext-xml": "*",
-    "leafo/scssphp": "0.7.4",
+    "leafo/scssphp": "0.7.6",
     "erusev/parsedown": "^1.6",
     "erusev/parsedown-extra": "^0.7.1",
     "pelago/emogrifier": "^2.0",

composer.lock

@@ -1,39 +1,39 @@
 {
     "_readme": [
         "This file locks the dependencies of your project to a known state",
-        "Read more about it at https://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file",
+        "Read more about it at https://getcomposer.org/doc/01-basic-usage.md#installing-dependencies",
         "This file is @generated automatically"
     ],
-    "content-hash": "e8398f79f58f50b7a8b7e006ff135656",
+    "content-hash": "81a1536f324a2095f1d8804dcee5c790",
     "packages": [
         {
             "name": "doctrine/instantiator",
-            "version": "1.0.5",
+            "version": "1.1.0",
             "source": {
                 "type": "git",
                 "url": "https://github.com/doctrine/instantiator.git",
-                "reference": "8e884e78f9f0eb1329e445619e04456e64d8051d"
+                "reference": "185b8868aa9bf7159f5f953ed5afb2d7fcdc3bda"
             },
             "dist": {
                 "type": "zip",
-                "url": "https://api.github.com/repos/doctrine/instantiator/zipball/8e884e78f9f0eb1329e445619e04456e64d8051d",
+                "url": "https://api.github.com/repos/doctrine/instantiator/zipball/185b8868aa9bf7159f5f953ed5afb2d7fcdc3bda",
-                "reference": "8e884e78f9f0eb1329e445619e04456e64d8051d",
+                "reference": "185b8868aa9bf7159f5f953ed5afb2d7fcdc3bda",
                 "shasum": ""
             },
             "require": {
-                "php": ">=5.3,<8.0-DEV"
+                "php": "^7.1"
             },
             "require-dev": {
                 "athletic/athletic": "~0.1.8",
                 "ext-pdo": "*",
                 "ext-phar": "*",
-                "phpunit/phpunit": "~4.0",
+                "phpunit/phpunit": "^6.2.3",
-                "squizlabs/php_codesniffer": "~2.0"
+                "squizlabs/php_codesniffer": "^3.0.2"
             },
             "type": "library",
             "extra": {
                 "branch-alias": {
-                    "dev-master": "1.0.x-dev"
+                    "dev-master": "1.2.x-dev"
                 }
             },
             "autoload": {
@@ -58,7 +58,7 @@
                 "constructor",
                 "instantiate"
             ],
-            "time": "2015-06-14T21:17:01+00:00"
+            "time": "2017-07-22T11:58:36+00:00"
         },
         {
             "name": "erusev/parsedown",
@@ -152,16 +152,16 @@
         },
         {
             "name": "leafo/scssphp",
-            "version": "v0.7.4",
+            "version": "v0.7.6",
             "source": {
                 "type": "git",
                 "url": "https://github.com/leafo/scssphp.git",
-                "reference": "d7296256bd1bfacb8bd24e69030fd5e187181835"
+                "reference": "585f6ae84de62ffecf69c23805f25d78d7e4b794"
             },
             "dist": {
                 "type": "zip",
-                "url": "https://api.github.com/repos/leafo/scssphp/zipball/d7296256bd1bfacb8bd24e69030fd5e187181835",
+                "url": "https://api.github.com/repos/leafo/scssphp/zipball/585f6ae84de62ffecf69c23805f25d78d7e4b794",
-                "reference": "d7296256bd1bfacb8bd24e69030fd5e187181835",
+                "reference": "585f6ae84de62ffecf69c23805f25d78d7e4b794",
                 "shasum": ""
             },
             "require": {
@@ -200,7 +200,7 @@
                 "scss",
                 "stylesheet"
             ],
-            "time": "2017-12-21T00:18:53+00:00"
+            "time": "2018-05-24T02:18:53+00:00"
         },
         {
             "name": "mustangostang/spyc",
@@ -254,25 +254,28 @@
         },
         {
             "name": "myclabs/deep-copy",
-            "version": "1.7.0",
+            "version": "1.8.1",
             "source": {
                 "type": "git",
                 "url": "https://github.com/myclabs/DeepCopy.git",
-                "reference": "3b8a3a99ba1f6a3952ac2747d989303cbd6b7a3e"
+                "reference": "3e01bdad3e18354c3dce54466b7fbe33a9f9f7f8"
             },
             "dist": {
                 "type": "zip",
-                "url": "https://api.github.com/repos/myclabs/DeepCopy/zipball/3b8a3a99ba1f6a3952ac2747d989303cbd6b7a3e",
+                "url": "https://api.github.com/repos/myclabs/DeepCopy/zipball/3e01bdad3e18354c3dce54466b7fbe33a9f9f7f8",
-                "reference": "3b8a3a99ba1f6a3952ac2747d989303cbd6b7a3e",
+                "reference": "3e01bdad3e18354c3dce54466b7fbe33a9f9f7f8",
                 "shasum": ""
             },
             "require": {
-                "php": "^5.6 || ^7.0"
+                "php": "^7.1"
+            },
+            "replace": {
+                "myclabs/deep-copy": "self.version"
             },
             "require-dev": {
                 "doctrine/collections": "^1.0",
                 "doctrine/common": "^2.6",
-                "phpunit/phpunit": "^4.1"
+                "phpunit/phpunit": "^7.1"
             },
             "type": "library",
             "autoload": {
@@ -295,28 +298,33 @@
                 "object",
                 "object graph"
             ],
-            "time": "2017-10-19T19:58:43+00:00"
+            "time": "2018-06-11T23:09:50+00:00"
         },
         {
             "name": "pelago/emogrifier",
-            "version": "v2.0.0",
+            "version": "v2.1.1",
             "source": {
                 "type": "git",
                 "url": "https://github.com/MyIntervals/emogrifier.git",
-                "reference": "8babf8ddbf348f26b29674e2f84db66ff7e3d95e"
+                "reference": "8ee7fb5ad772915451ed3415c1992bd3697d4983"
             },
             "dist": {
                 "type": "zip",
-                "url": "https://api.github.com/repos/MyIntervals/emogrifier/zipball/8babf8ddbf348f26b29674e2f84db66ff7e3d95e",
+                "url": "https://api.github.com/repos/MyIntervals/emogrifier/zipball/8ee7fb5ad772915451ed3415c1992bd3697d4983",
-                "reference": "8babf8ddbf348f26b29674e2f84db66ff7e3d95e",
+                "reference": "8ee7fb5ad772915451ed3415c1992bd3697d4983",
                 "shasum": ""
             },
             "require": {
-                "php": "^5.5.0 || ~7.0.0 || ~7.1.0 || ~7.2.0"
+                "ext-dom": "*",
+                "ext-libxml": "*",
+                "php": "^5.5.0 || ~7.0.0 || ~7.1.0 || ~7.2.0 || ~7.3.0",
+                "symfony/css-selector": "^3.4.0 || ^4.0.0"
             },
             "require-dev": {
+                "friendsofphp/php-cs-fixer": "^2.2.0",
+                "phpmd/phpmd": "^2.6.0",
                 "phpunit/phpunit": "^4.8.0",
-                "squizlabs/php_codesniffer": "^3.1.0"
+                "squizlabs/php_codesniffer": "^3.3.2"
             },
             "type": "library",
             "extra": {
@@ -326,7 +334,7 @@
             },
             "autoload": {
                 "psr-4": {
-                    "Pelago\\": "Classes/"
+                    "Pelago\\": "src/"
                 }
             },
             "notification-url": "https://packagist.org/downloads/",
@@ -344,10 +352,6 @@
                 {
                     "name": "Jaime Prado"
                 },
-                {
-                    "name": "Roman Ožana",
-                    "email": "ozana@omdesign.cz"
-                },
                 {
                     "name": "Oliver Klee",
                     "email": "github@oliverklee.de"
@@ -355,6 +359,10 @@
                 {
                     "name": "Zoli Szabó",
                     "email": "zoli.szabo+github@gmail.com"
+                },
+                {
+                    "name": "Jake Hotson",
+                    "email": "jake@qzdesign.co.uk"
                 }
             ],
             "description": "Converts CSS styles into inline style attributes in your HTML code",
@@ -364,7 +372,7 @@
                 "email",
                 "pre-processing"
             ],
-            "time": "2018-01-05T23:30:21+00:00"
+            "time": "2018-12-10T10:36:30+00:00"
         },
         {
             "name": "phar-io/manifest",
@@ -622,33 +630,33 @@
         },
         {
             "name": "phpspec/prophecy",
-            "version": "1.7.5",
+            "version": "1.8.0",
             "source": {
                 "type": "git",
                 "url": "https://github.com/phpspec/prophecy.git",
-                "reference": "dfd6be44111a7c41c2e884a336cc4f461b3b2401"
+                "reference": "4ba436b55987b4bf311cb7c6ba82aa528aac0a06"
             },
             "dist": {
                 "type": "zip",
-                "url": "https://api.github.com/repos/phpspec/prophecy/zipball/dfd6be44111a7c41c2e884a336cc4f461b3b2401",
+                "url": "https://api.github.com/repos/phpspec/prophecy/zipball/4ba436b55987b4bf311cb7c6ba82aa528aac0a06",
-                "reference": "dfd6be44111a7c41c2e884a336cc4f461b3b2401",
+                "reference": "4ba436b55987b4bf311cb7c6ba82aa528aac0a06",
                 "shasum": ""
             },
             "require": {
                 "doctrine/instantiator": "^1.0.2",
                 "php": "^5.3|^7.0",
                 "phpdocumentor/reflection-docblock": "^2.0|^3.0.2|^4.0",
-                "sebastian/comparator": "^1.1|^2.0",
+                "sebastian/comparator": "^1.1|^2.0|^3.0",
                 "sebastian/recursion-context": "^1.0|^2.0|^3.0"
             },
             "require-dev": {
                 "phpspec/phpspec": "^2.5|^3.2",
-                "phpunit/phpunit": "^4.8.35 || ^5.7 || ^6.5"
+                "phpunit/phpunit": "^4.8.35 || ^5.7 || ^6.5 || ^7.1"
             },
             "type": "library",
             "extra": {
                 "branch-alias": {
-                    "dev-master": "1.7.x-dev"
+                    "dev-master": "1.8.x-dev"
                 }
             },
             "autoload": {
@@ -681,20 +689,20 @@
                 "spy",
                 "stub"
             ],
-            "time": "2018-02-19T10:16:54+00:00"
+            "time": "2018-08-05T17:53:17+00:00"
         },
         {
             "name": "phpunit/php-code-coverage",
-            "version": "5.3.0",
+            "version": "5.3.2",
             "source": {
                 "type": "git",
                 "url": "https://github.com/sebastianbergmann/php-code-coverage.git",
-                "reference": "661f34d0bd3f1a7225ef491a70a020ad23a057a1"
+                "reference": "c89677919c5dd6d3b3852f230a663118762218ac"
             },
             "dist": {
                 "type": "zip",
-                "url": "https://api.github.com/repos/sebastianbergmann/php-code-coverage/zipball/661f34d0bd3f1a7225ef491a70a020ad23a057a1",
+                "url": "https://api.github.com/repos/sebastianbergmann/php-code-coverage/zipball/c89677919c5dd6d3b3852f230a663118762218ac",
-                "reference": "661f34d0bd3f1a7225ef491a70a020ad23a057a1",
+                "reference": "c89677919c5dd6d3b3852f230a663118762218ac",
                 "shasum": ""
             },
             "require": {
@@ -744,7 +752,7 @@
                 "testing",
                 "xunit"
             ],
-            "time": "2017-12-06T09:29:45+00:00"
+            "time": "2018-04-06T15:36:58+00:00"
         },
         {
             "name": "phpunit/php-file-iterator",
@@ -934,16 +942,16 @@
         },
         {
             "name": "phpunit/phpunit",
-            "version": "6.5.7",
+            "version": "6.5.13",
             "source": {
                 "type": "git",
                 "url": "https://github.com/sebastianbergmann/phpunit.git",
-                "reference": "6bd77b57707c236833d2b57b968e403df060c9d9"
+                "reference": "0973426fb012359b2f18d3bd1e90ef1172839693"
             },
             "dist": {
                 "type": "zip",
-                "url": "https://api.github.com/repos/sebastianbergmann/phpunit/zipball/6bd77b57707c236833d2b57b968e403df060c9d9",
+                "url": "https://api.github.com/repos/sebastianbergmann/phpunit/zipball/0973426fb012359b2f18d3bd1e90ef1172839693",
-                "reference": "6bd77b57707c236833d2b57b968e403df060c9d9",
+                "reference": "0973426fb012359b2f18d3bd1e90ef1172839693",
                 "shasum": ""
             },
             "require": {
@@ -961,7 +969,7 @@
                 "phpunit/php-file-iterator": "^1.4.3",
                 "phpunit/php-text-template": "^1.2.1",
                 "phpunit/php-timer": "^1.0.9",
-                "phpunit/phpunit-mock-objects": "^5.0.5",
+                "phpunit/phpunit-mock-objects": "^5.0.9",
                 "sebastian/comparator": "^2.1",
                 "sebastian/diff": "^2.0",
                 "sebastian/environment": "^3.1",
@@ -1014,20 +1022,20 @@
                 "testing",
                 "xunit"
             ],
-            "time": "2018-02-26T07:01:09+00:00"
+            "time": "2018-09-08T15:10:43+00:00"
         },
         {
             "name": "phpunit/phpunit-mock-objects",
-            "version": "5.0.6",
+            "version": "5.0.10",
             "source": {
                 "type": "git",
                 "url": "https://github.com/sebastianbergmann/phpunit-mock-objects.git",
-                "reference": "33fd41a76e746b8fa96d00b49a23dadfa8334cdf"
+                "reference": "cd1cf05c553ecfec36b170070573e540b67d3f1f"
             },
             "dist": {
                 "type": "zip",
-                "url": "https://api.github.com/repos/sebastianbergmann/phpunit-mock-objects/zipball/33fd41a76e746b8fa96d00b49a23dadfa8334cdf",
+                "url": "https://api.github.com/repos/sebastianbergmann/phpunit-mock-objects/zipball/cd1cf05c553ecfec36b170070573e540b67d3f1f",
-                "reference": "33fd41a76e746b8fa96d00b49a23dadfa8334cdf",
+                "reference": "cd1cf05c553ecfec36b170070573e540b67d3f1f",
                 "shasum": ""
             },
             "require": {
@@ -1040,7 +1048,7 @@
                 "phpunit/phpunit": "<6.0"
             },
             "require-dev": {
-                "phpunit/phpunit": "^6.5"
+                "phpunit/phpunit": "^6.5.11"
             },
             "suggest": {
                 "ext-soap": "*"
@@ -1073,7 +1081,7 @@
                 "mock",
                 "xunit"
             ],
-            "time": "2018-01-06T05:45:45+00:00"
+            "time": "2018-08-09T05:50:03+00:00"
         },
         {
             "name": "sebastian/code-unit-reverse-lookup",
@@ -1634,6 +1642,117 @@
             "homepage": "https://github.com/sebastianbergmann/version",
             "time": "2016-10-03T07:35:21+00:00"
         },
+        {
+            "name": "symfony/css-selector",
+            "version": "v4.2.2",
+            "source": {
+                "type": "git",
+                "url": "https://github.com/symfony/css-selector.git",
+                "reference": "76dac1dbe2830213e95892c7c2ec1edd74113ea4"
+            },
+            "dist": {
+                "type": "zip",
+                "url": "https://api.github.com/repos/symfony/css-selector/zipball/76dac1dbe2830213e95892c7c2ec1edd74113ea4",
+                "reference": "76dac1dbe2830213e95892c7c2ec1edd74113ea4",
+                "shasum": ""
+            },
+            "require": {
+                "php": "^7.1.3"
+            },
+            "type": "library",
+            "extra": {
+                "branch-alias": {
+                    "dev-master": "4.2-dev"
+                }
+            },
+            "autoload": {
+                "psr-4": {
+                    "Symfony\\Component\\CssSelector\\": ""
+                },
+                "exclude-from-classmap": [
+                    "/Tests/"
+                ]
+            },
+            "notification-url": "https://packagist.org/downloads/",
+            "license": [
+                "MIT"
+            ],
+            "authors": [
+                {
+                    "name": "Jean-François Simon",
+                    "email": "jeanfrancois.simon@sensiolabs.com"
+                },
+                {
+                    "name": "Fabien Potencier",
+                    "email": "fabien@symfony.com"
+                },
+                {
+                    "name": "Symfony Community",
+                    "homepage": "https://symfony.com/contributors"
+                }
+            ],
+            "description": "Symfony CssSelector Component",
+            "homepage": "https://symfony.com",
+            "time": "2019-01-03T09:07:35+00:00"
+        },
+        {
+            "name": "symfony/polyfill-ctype",
+            "version": "v1.10.0",
+            "source": {
+                "type": "git",
+                "url": "https://github.com/symfony/polyfill-ctype.git",
+                "reference": "e3d826245268269cd66f8326bd8bc066687b4a19"
+            },
+            "dist": {
+                "type": "zip",
+                "url": "https://api.github.com/repos/symfony/polyfill-ctype/zipball/e3d826245268269cd66f8326bd8bc066687b4a19",
+                "reference": "e3d826245268269cd66f8326bd8bc066687b4a19",
+                "shasum": ""
+            },
+            "require": {
+                "php": ">=5.3.3"
+            },
+            "suggest": {
+                "ext-ctype": "For best performance"
+            },
+            "type": "library",
+            "extra": {
+                "branch-alias": {
+                    "dev-master": "1.9-dev"
+                }
+            },
+            "autoload": {
+                "psr-4": {
+                    "Symfony\\Polyfill\\Ctype\\": ""
+                },
+                "files": [
+                    "bootstrap.php"
+                ]
+            },
+            "notification-url": "https://packagist.org/downloads/",
+            "license": [
+                "MIT"
+            ],
+            "authors": [
+                {
+                    "name": "Symfony Community",
+                    "homepage": "https://symfony.com/contributors"
+                },
+                {
+                    "name": "Gert de Pagter",
+                    "email": "BackEndTea@gmail.com"
+                }
+            ],
+            "description": "Symfony polyfill for ctype functions",
+            "homepage": "https://symfony.com",
+            "keywords": [
+                "compatibility",
+                "ctype",
+                "polyfill",
+                "portable"
+            ],
+            "time": "2018-08-06T14:22:27+00:00"
+        },
         {
             "name": "theseer/tokenizer",
             "version": "1.1.0",
@@ -1676,20 +1795,21 @@
         },
         {
             "name": "webmozart/assert",
-            "version": "1.3.0",
+            "version": "1.4.0",
             "source": {
                 "type": "git",
                 "url": "https://github.com/webmozart/assert.git",
-                "reference": "0df1908962e7a3071564e857d86874dad1ef204a"
+                "reference": "83e253c8e0be5b0257b881e1827274667c5c17a9"
             },
             "dist": {
                 "type": "zip",
-                "url": "https://api.github.com/repos/webmozart/assert/zipball/0df1908962e7a3071564e857d86874dad1ef204a",
+                "url": "https://api.github.com/repos/webmozart/assert/zipball/83e253c8e0be5b0257b881e1827274667c5c17a9",
-                "reference": "0df1908962e7a3071564e857d86874dad1ef204a",
+                "reference": "83e253c8e0be5b0257b881e1827274667c5c17a9",
                 "shasum": ""
             },
             "require": {
-                "php": "^5.3.3 || ^7.0"
+                "php": "^5.3.3 || ^7.0",
+                "symfony/polyfill-ctype": "^1.8"
             },
             "require-dev": {
                 "phpunit/phpunit": "^4.6",
@@ -1722,7 +1842,7 @@
                 "check",
                 "validate"
             ],
-            "time": "2018-01-29T19:49:41+00:00"
+            "time": "2018-12-25T11:19:39+00:00"
         }
     ],
     "packages-dev": [],

content/bio/akinwale-ariwodola.md

@@ -5,8 +5,9 @@ email: akinwale@lbry.io
 twitter: akinwale
 github: akinwale
 ---
+
 It was Akinwale’s search for lucrative crypto mining that brought him to LBRY. As he learned more about the project, his interest quickly turned to helping the team build the content sharing platform of the future.
 
-Akinwale has worked on everything from rewriting a new block explorer from the ground up, improvements to the app’s interface, as well as leading the effort to successfully get the daemon running on Android. 
+Akinwale has worked on everything from rewriting a new block explorer from the ground up, improvements to the app’s interface, as well as leading the effort to successfully get the daemon running on Android.
 
 When he’s not working on LBRY, he actively participates in competitive programming contests on Topcoder, and is a two-time champion of the annual Topcoder Open event.

content/bio/alex-liebowitz.md

@@ -3,6 +3,7 @@ name: Alex Liebowitz
 role: App Developer
 email: aliebowitz@lbry.io
 ---
+
 Alex is responsible for the LBRY browsing application. An economist turned web developer, Alex joins an assortment of polymaths at LBRY.
 
-Prior to joining LBRY, Alex helped build web and mobile apps for large national corporations. Alex also helps run a large podcasting network and brings knowledge and experience of the publishing industry.
+Prior to joining LBRY, Alex helped build web and mobile apps for large national corporations. Alex also helps run a large podcasting network and brings knowledge and experience of the publishing industry.

content/bio/alex-tabarrok.md

@@ -2,8 +2,9 @@
 name: Alex Tabarrok
 role: Economic Advisor
 ---
-Alex Tabarrok is Bartley J. Madden Chair in Economics at the [Mercatus Center](http://mercatus.org/) and a professor of economics at [George Mason University](https://gmu.edu). He specializes in intellectual property reform, the effectiveness of markets, and the justice system.
 
-Tabarrok is the coauthor, with Mercatus colleague Tyler Cowen, of the popular economics blog [_Marginal Revolution_](http://www.marginalrevolution.com/) and cofounder of the online educational platform [Marginal Revolution University](http://mruniversity.com/). He is the coauthor of _[Modern Principles of Economics](http://www.amazon.com/Modern-Principles-Economics-Tyler-Cowen/dp/1429239972)_, and author of the recent book _[Launching the Innovation Renaissance](http://www.amazon.com/Launching-The-Innovation-Renaissance-Market-ebook/dp/B006C1HX24)_. His articles have appeared in the _New York Times_, the _Washington Post_, the _Wall Street Journal_, and many other prestigious publications.
+Alex Tabarrok is Bartley J. Madden Chair in Economics at the [Mercatus Center](http://mercatus.org) and a professor of economics at [George Mason University](https://gmu.edu). He specializes in intellectual property reform, the effectiveness of markets, and the justice system.
 
-Tabarrok received his PhD in economics from [George Mason University](http://en.wikipedia.org/wiki/George_Mason_University "George Mason University").
+Tabarrok is the coauthor, with Mercatus colleague Tyler Cowen, of the popular economics blog [_Marginal Revolution_](http://www.marginalrevolution.com) and cofounder of the online educational platform [Marginal Revolution University](http://mruniversity.com). He is the coauthor of _[Modern Principles of Economics](http://www.amazon.com/Modern-Principles-Economics-Tyler-Cowen/dp/1429239972)_, and author of the recent book _[Launching the Innovation Renaissance](http://www.amazon.com/Launching-The-Innovation-Renaissance-Market-ebook/dp/B006C1HX24)_. His articles have appeared in the _New York Times_, the _Washington Post_, the _Wall Street Journal_, and many other prestigious publications.
+
+Tabarrok received his PhD in economics from [George Mason University](http://en.wikipedia.org/wiki/George_Mason_University "George Mason University").

content/bio/amit-tulshyan.md

@@ -5,6 +5,7 @@ email: hackrush@lbry.io
 twitter: amittulshyan
 github: hackrush01
 ---
+
 Amit arrived at LBRY through mining. Diving into the world of cryptocurrency, he discovered LBRY Credits amongst the most profitable to mine. A few Slack messages later, he was making pull requests to the backend python code on GitHub.
 
 When he’s not contributing his talents to LBRY, he loves practicing synth, guitar, and deeply contemplating quantum computing. 

content/bio/bill-bittner.md

@@ -5,8 +5,9 @@ email: bill@lbry.io
 twitter: billbitt2000
 github: billbitt
 ---
-Bill's primary contributions were to [spee.ch](https://spee.ch), an open-source web application built on the LBRY Protocol. 
 
-Bill’s long-standing fascination with web applications eventually led him to utility-driven blockchains and, naturally, LBRY. 
+Bill's primary contributions were to [spee.ch](https://spee.ch), an open-source web application built on the LBRY Protocol.
+
+Bill’s long-standing fascination with web applications eventually led him to utility-driven blockchains and, naturally, LBRY.
 
 When he is not hacking on web apps, he enjoys drawing, playing soccer, and slowly working his way through his Steam library.

content/bio/brinck-slattery.md

@@ -5,8 +5,9 @@ email: brinck@lbry.io
 twitter: LazerLotus777
 github: Feanor78
 ---
-Brinck’s range of experience includes national political campaigns, crisis PR, SEO writing and optimization, digital marketing, RV sales, construction labor, and a variety of other strange and interesting pursuits (feel free to ask). 
 
-An inveterate music and media lover, Brinck remembers the pain of Kazaa and Limewire, and is seriously psyched about living in the future where it’s easy to compensate artists directly for their work. 
+Brinck’s range of experience includes national political campaigns, crisis PR, SEO writing and optimization, digital marketing, RV sales, construction labor, and a variety of other strange and interesting pursuits (feel free to ask).
+
+An inveterate music and media lover, Brinck remembers the pain of Kazaa and Limewire, and is seriously psyched about living in the future where it’s easy to compensate artists directly for their work.
 
 He lives in Manchester, NH and can be regularly found lurking wherever the latest music is blaring.

content/bio/igor-gassmann.md

@@ -5,8 +5,9 @@ email: igor@lbry.io
 twitter: i_gassmann
 github: IGassmann
 ---
+
 Igor primarily contributed to the application. By the time he turned 16, Igor’s driving passion was clear (and it was not high school). So, he dropped out, and moved to Switzerland to build a career in software development.
 
-It was Igor’s participation in [Praxis programs](http://discoverpraxis.com/) that led him to LBRY. His long time interest in the crypto market and blockchain technology, coupled with his desire to work in a start-up environment, made LBRY seemed like a perfect fit (and the team agreed!). 
+It was Igor’s participation in [Praxis programs](http://discoverpraxis.com) that led him to LBRY. His long time interest in the crypto market and blockchain technology, coupled with his desire to work in a start-up environment, made LBRY seemed like a perfect fit (and the team agreed!).
 
 When he is not coding, Igor enjoys discussing economics, philosophy, and politics.

content/bio/jack-robison.md

@@ -4,6 +4,7 @@ role: Founder, Protocol Developer
 email: jack@lbry.io
 github: jackrobison
 ---
+
 Jack's path to developer with LBRY is fairly typical: [face sixty years in prison for innocent chemistry experiments](http://www.masslive.com/localbuzz/index.ssf/2009/06/actionreaction_how_one_teens_c.html); lose interest in chemistry; [program insane electric guitars for Kiss](https://www.youtube.com/watch?v=dXZi4UZjiiI&t=10); decide to revolutionize the internet.
 
 Jack was one of the first people to discover LBRY and took to it so fast he may understand more about it than anyone.

content/bio/james-biller.md

@@ -5,7 +5,8 @@ email: james@lbry.io
 twitter: billerjames
 github: jamesbiller
 ---
-James came to LBRY through Praxis, a company that offers apprenticeships to young entrepreneurial types. 
+
+James came to LBRY through Praxis, a company that offers apprenticeships to young entrepreneurial types.
 
 Originally brought on to help with recruiting YouTubers, James showed up to the office with a 3D printed LBRYopoly board and was the original person who championed the use of the LBRY protocol for 3D printing.
 

content/bio/jimmy-kiselak.md

@@ -3,8 +3,9 @@ name: Jimmy Kiselak
 role: Founder, Core Developer
 email: jimmy@lbry.io
 ---
+
 Jimmy is the second comp science/physics graduate from Rensselaer. After, he found himself mired in government bureaucracy, spending too much time to get too little done.
 
 Ready to work on a project he believed in, Jimmy left a national security programming job to start LBRY. Jimmy created the LBRY protocol and the first LBRY application.
 
-Jimmy is a Bitcoin fanatic and has been since its early days. He has long been interested in the benefits of decentralization.
+Jimmy is a Bitcoin fanatic and has been since its early days. He has long been interested in the benefits of decentralization.

content/bio/job-evers-meltzer.md

@@ -3,6 +3,7 @@ name: Job Evers-Meltzer
 role: VP of Engineering
 email: jobevers@lbry.io
 ---
+
 Job was early to discover LBRY and made himself indispensable almost immediately. Job manages the engineering team, project roadmap, and reviews most code changes. Job also handles LBRY builds, quality assurance, analytics, and an assortment of ad hoc projects.
 
 Job attended the Massachusetts Institute of Technology, where he obtained a degree in mathematics. Job has experience in quantitative finance, analytical development, and data engineering.

content/bio/josh-finer.md

@@ -5,7 +5,8 @@ email: josh@lbry.io
 twitter: finer9
 github: finer9
 ---
-Josh is the swiss army knife of the squad. 
+
+Josh is the swiss army knife of the squad.
 
 He has founded and sold financial companies, run millions of dollars in Adwords campaigns, and been an early actor in several crypto projects. 
 

content/bio/kay-kurokawa.md

@@ -5,6 +5,7 @@ email: kay@lbry.io
 twitter: kaykurokawa
 github: kaykurokawa
 ---
+
 Kay Kurokawa contributes to the LBRY blockchain, the foundation of the LBRY protocol. Kay first discovered Bitcoin in 2013 and immediately saw its potential. Before LBRY, he provided consultation services to blockchain startups and contributed to various open source projects such as Electrum, Litecoin, Dogecoin, and Blocknet.
 
 Before his work on blockchain technology, Kay worked at a high frequency trading firm as a software engineer. He also spent time developing algorithms for spectrometry devices, and has several published papers on the topic. He earned a B.S. and an M.S. from Carnegie Mellon University in electrical and computer engineering.

content/bio/lex-berezhny.md

@@ -5,6 +5,7 @@ email: lex@lbry.io
 twitter: eukreign
 github: eukreign
 ---
-Lex learned to write Python in High School, not far from where the language was first created, and even participated in some of the first Python user groups hosted by Guido, himself. In 2000, still a very young man, Lex gave his first public talk, titled “Yorktown High School Becomes a Python Workshop” at the International Python Conference. Needless to say, Lex and Python go way back.
+
+Lex learned to write Python in High School, not far from where the language was first created, and even participated in some of the first Python user groups hosted by Guido, himself. In 2000, still a very young man, Lex gave his first public talk, titled "Yorktown High School Becomes a Python Workshop" at the International Python Conference. Needless to say, Lex and Python go way back.
 
 Lex spends his time on the full stack of LBRY backends, such as the wallet, protocol, and blockchain, and is currently wading deep into the improvement of test coverage and performance of various LBRY components. If you want to trade notes on Dart, and dish on a possible ideal use case for Dart at LBRY, Lex wants to hear from you!

content/bio/liam-cardenas.md

@@ -5,8 +5,9 @@ email: liam@lbry.io
 twitter: ljcio
 github: liamcardenas
 ---
+
 As a lifelong entrepreneur and crypto-anarchist, the LBRY project was of high interest to Liam on many levels – meeting the team and learning more about app development goals made his decision to become a full-fledged LBRYian an easy one.
 
-Liam’s sincere passion for making distributed censorship-resistant software easy to use has been a boon to the team. 
+Liam’s sincere passion for making distributed censorship-resistant software easy to use has been a boon to the team.
 
 In addition to his work with LBRY, Liam is also an advisor to several startups and blockchain projects.

content/bio/mark-beamer.md

@@ -5,9 +5,9 @@ email: mark@lbry.io
 github: tiger5226
 ---
 
-Mark Beamer is an inveterate entrepreneur. Ever since he founded his first company (Beamer Lawn Service) at 16, he's pursued new and interesting business ideas. 
+Mark Beamer is an inveterate entrepreneur. Ever since he founded his first company (Beamer Lawn Service) at 16, he's pursued new and interesting business ideas.
 
-While running his first computer business, Mark discovered the joys of coding - especially the joys of using coding to eliminate annoying tasks with automation. 
+While running his first computer business, Mark discovered the joys of coding - especially the joys of using coding to eliminate annoying tasks with automation.
 
 His continued passion for software led him to close the business after 4 years and pursue a BS in computational science and mathematics.
 

content/bio/michael-huemer.md

@@ -2,6 +2,7 @@
 name: Michael Huemer
 role: Ethics Advisor
 ---
-Michael Huemer is Professor of Philosophy and Ethics at the [University of Colorado](//www.colorado.edu/), where he has taught since 1998\. He has published three single-author scholarly books (including _[Ethical Intuitionism](http://www.amazon.com/Ethical-Intuitionism-Michael-Huemer/dp/0230573746)_), one edited anthology, and more than fifty academic articles in epistemology, ethics, political philosophy, and metaphysics.
+
+Michael Huemer is Professor of Philosophy and Ethics at the [University of Colorado](//www.colorado.edu), where he has taught since 1998\. He has published three single-author scholarly books (including _[Ethical Intuitionism](http://www.amazon.com/Ethical-Intuitionism-Michael-Huemer/dp/0230573746)_), one edited anthology, and more than fifty academic articles in epistemology, ethics, political philosophy, and metaphysics.
 
 Huemer's articles have appeared in such journals as the _Philosophical Review_, _Mind_, the _Journal of Philosophy_, _Ethics_, and others. His materials are used as readings in classrooms nationwide. He received a B.A. from UC Berkeley and a Ph.D. from Rutgers University.

content/bio/mike-vine.md

@@ -3,6 +3,7 @@ name: Mike Vine
 role: .
 email: hello@lbry.io
 ---
+
 Mike was one of the early team members of LBRY.
 
 He contributed to marketing and branding in the earliest days of the app.

content/bio/natalie-mitchell.md

@@ -3,8 +3,9 @@ name: Natalie Mitchell
 role: Former Director of Growth and Branding
 email: natalie@lbry.io
 twitter: blockchainbandi
-github: blckchnprncss 
+github: blckchnprncss
 ---
+
 Natalie has been interested in blockchain technology and open-source everything since the early days of Bitcoin, and has been recruiting, managing operations, and coaching top notch talent to success for even longer.
 
 She contributed to procedures, and communications efforts that help the team to work to its potential and remain efficient as the LBRY project grows. 

content/bio/niko-storni.md

@@ -5,10 +5,11 @@ email: Niko@lbry.io
 twitter: Nikooo777
 github: Nikooo777
 ---
-Niko isn't scared of putting his hands in the code to write solutions to make user’s lives easier. 
 
-After graduating as an IT Engineer in Switzerland, Niko joined the LBRY community as a miner and volunteer contributor for almost 2 years before quitting his job to pursue his real passion: LBRY. 
+Niko isn't scared of putting his hands in the code to write solutions to make user’s lives easier.
 
-Running a gaming community for almost 10 years, Niko has developed a lot of experience with managing and serving professional solutions on Linux servers. 
+After graduating as an IT Engineer in Switzerland, Niko joined the LBRY community as a miner and volunteer contributor for almost 2 years before quitting his job to pursue his real passion: LBRY.
+
+Running a gaming community for almost 10 years, Niko has developed a lot of experience with managing and serving professional solutions on Linux servers.
 
 Together with his professional background, he is in charge of providing LBRY with the right server infrastructure, vital for everyone to enjoy a smooth and safe experience. When he's not sitting behind a monitor, Niko enjoys riding his motorcycle, hiking the Alps, reading, swimming, and much more!

content/bio/ray-carballada.md

@@ -2,9 +2,10 @@
 name: Ray Carballada
 role: Media Advisor
 ---
+
 Ray Carballada is a creative, accomplished senior business leader in the converging worlds of content: advertising, television, motion pictures, social, and online media.
 
 As former CEO of Alkemy X, Ray led its transformation from a small production company into a fully integrated creative content company with offices in Philadelphia and New York.  Clients include global ad agencies such as BBDO, Gray, and 360i; Fortune 500 brands including Campbell Soup, Samsung, Pepsi and BMW; TV networks including Discovery, Food Network, and HBO; and motion picture studios including Sony and the Weinstein Company.
 
-Alkemy X made the INC 5000 list of the fastest growing companies in the U.S. six times since 2008, and received the “Creative Economy Award for Distinction" from the Arts and Business Council of Greater Philadelphia, as well as 60 Addy and Emmy awards, among others. Ray received his BS in Photography from Rochester Institute of Technology and a Masters in Business Administration from Bucknell University.
+Alkemy X made the INC 5000 list of the fastest growing companies in the U.S. six times since 2008, and received the "Creative Economy Award for Distinction" from the Arts and Business Council of Greater Philadelphia, as well as 60 Addy and Emmy awards, among others. Ray received his BS in Photography from Rochester Institute of Technology and a Masters in Business Administration from Bucknell University.
 

content/bio/reilly-smith-youtube.md

@@ -3,6 +3,7 @@ name: Reilly Smith
 role: Former Community Manager
 email: reilly@lbry.io
 ---
+
 Reilly holds a BA in Film and Media Studies from the University of Oklahoma and consequently has spent a significant amount of time washing dishes.
 
 His films have shown at Sundance, SXSW, Dallas IFF, and LA Film Fest and he has produced series for Zero Day Fox and Disney.

content/bio/reilly-smith.md

@@ -5,10 +5,11 @@ email: reilly@lbry.io
 twitter: reillysmith
 github: reillysmith
 ---
-For nearly a decade, Reilly has developed, produced, championed and contributed to dozens of film projects big and small. 
 
-The only thing that rivals his love of film is the marriage between content and blockchain. 
+For nearly a decade, Reilly has developed, produced, championed and contributed to dozens of film projects big and small.
 
-If you come from the world of film, television or web content, he's your sherpa on Mount Blockchain. 
+The only thing that rivals his love of film is the marriage between content and blockchain.
+
+If you come from the world of film, television or web content, he's your sherpa on Mount Blockchain.
 
 Reilly's work has been seen from Oxford, Mississippi to Sundance Film Festival, and he has produced content for Fox Digital Studios and Disney LOL.

content/bio/samuel-lbryian.md

@@ -5,4 +5,5 @@ email: hello@lbry.io
 twitter: lbryio
 github: lbryio
 ---
+
 Much of our writing is a collaboration between LBRY team members, so we use SamueL BRYan to share credit. Sam has become a friend... an imaginary friend... even though we're adults...

content/bio/sean-yesmunt.md

@@ -5,8 +5,9 @@ email: sean@lbry.io
 twitter: seanyesmunt
 github: seanyesmunt
 ---
+
 Sean is an app engineer focused on user experience, which means he spends his time making the LBRY app easier to use. Sean was part way through an Aerospace Engineering degree at Penn State, when he decided he didn’t want to end up working on rockets for the government.
 
-So, he did what many LBRYians have done, and dropped out to focus on coding. His excitement for crypto and open-source projects focused on decentralization, led him to discover LBRY, which he began working on the very same day. 
+So, he did what many LBRYians have done, and dropped out to focus on coding. His excitement for crypto and open-source projects focused on decentralization, led him to discover LBRY, which he began working on the very same day.
 
 His passion for developing intuitive experiences has brought immense value to users all around the world who use LBRY.

content/bio/stephan-kinsella.md

@@ -2,6 +2,7 @@
 name: Stephan Kinsella
 role: Legal Advisor
 ---
-Stephan Kinsella is a registered patent attorney and has over twenty years’ experience in patent, intellectual property, and general commercial and corporate law. He is the founder and director of the [Center for the Study of Innovative Freedom](http://c4sif.org/). Kinsella has published numerous articles and books on intellectual property law and legal topics including [_International Investment, Political Risk, and Dispute Resolution: A Practitioner’s Guide_](http://www.amazon.com/International-Investment-Political-Dispute-Resolution/dp/0379215225) and [_Against Intellectual Property_](https://mises.org/library/against-intellectual-property-0) .
 
-He received an LL.M. in international business law from [King’s College London](http://www.kcl.ac.uk/), a JD from the Paul M. Hebert Law Center at [Louisiana State University](//lsu.edu), as well as BSEE and MSEE degrees. His websites are [stephankinsella.com](http://stephankinsella.com) and [kinsellalaw.com](http://kinsellalaw.com)
+Stephan Kinsella is a registered patent attorney and has over twenty years' experience in patent, intellectual property, and general commercial and corporate law. He is the founder and director of the [Center for the Study of Innovative Freedom](http://c4sif.org). Kinsella has published numerous articles and books on intellectual property law and legal topics including [_International Investment, Political Risk, and Dispute Resolution: A Practitioner's Guide_](http://www.amazon.com/International-Investment-Political-Dispute-Resolution/dp/0379215225) and [_Against Intellectual Property_](https://mises.org/library/against-intellectual-property-0) .
+
+He received an LL.M. in international business law from [King's College London](http://www.kcl.ac.uk), a JD from the Paul M. Hebert Law Center at [Louisiana State University](//lsu.edu), as well as BSEE and MSEE degrees. His websites are [stephankinsella.com](http://stephankinsella.com) and [kinsellalaw.com](http://kinsellalaw.com)

content/bio/tom-zarebczan.md

@@ -5,6 +5,7 @@ email: tom@lbry.io
 twitter: TomZarebczan
 github : tzarebczan
 ---
+
 Tom discovered LBRY, as many have, through mining. His time spent in the LBRY Slack channels quickly grew his interest in the concept that was being developed, and the team doing the development. Tom found his place on the team providing top-notch support for (and driving the growth of) the LBRY user community, in addition to many other invaluable functions.
 
-Tom holds a Bachelors in Computer Engineering from the New Jersey Institute of Technology, a Masters in Systems Engineering from Stevens Institute of Technology, and served his country proudly as a Civilian in the US Army for 7 years. When he’s not monitoring LBRY Twitter, Reddit, Slack, and/or Discord looking for users in distress, Tom can be found doing geek-y stuff, or snowboarding in really cool places around the world.
+Tom holds a Bachelors in Computer Engineering from the New Jersey Institute of Technology, a Masters in Systems Engineering from Stevens Institute of Technology, and served his country proudly as a Civilian in the US Army for 7 years. When he's not monitoring LBRY Twitter, Reddit, Slack, and/or Discord looking for users in distress, Tom can be found doing geek-y stuff, or snowboarding in really cool places around the world.

content/bio/you.md

@@ -3,8 +3,9 @@ name: You
 role: Developer, Designer, Economist, Marketer, Investor, ???
 email: jeremy@lbry.io
 ---
+
 Do you think opening up information would facilitate human flourishing?
 
 Do you want to join a bright core of people with an obsession for upending broken systems?
 
-[Say hello](mailto:jeremy@lbry.io).
+[Say hello](mailto:jeremy@lbry.io).

content/bounty/bulk-upload.md

@@ -5,9 +5,10 @@ award: 500
 status: completed
 date: '2018-03-20'
 ---
-Completed in: https://github.com/marcdeb1/lbry_uploader   
 
-This bounty is to create a utility that can bulk upload a series of videos to LBRY. A LBRY term intern started implementing this in https://github.com/filipnyquist/lbrysync - this can be used as a base to fill in the rest of the required features. 
+Completed in: https://github.com/marcdeb1/lbry_uploader
+
+This bounty is to create a utility that can bulk upload a series of videos to LBRY. A LBRY term intern started implementing this in https://github.com/filipnyquist/lbrysync - this can be used as a base to fill in the rest of the required features.
 
 This utility is for semi-technical users who have a large amount of content they want to sync. A good example use case would be the videos from a conference.
 

content/bounty/fourohfour-page.md

@@ -6,8 +6,8 @@ status: complete
 date: '2017-09-07'
 ---
 
-Our 404 page is very bland. We'd like something that's more 
+Our 404 page is very bland. We'd like something that's more
- 
+
 - **helpful** - tell the user what happened, and give them some things to do next
 - **pretty** - we spent very little time on the one we have
 - **humorous** - everyone likes funny things

content/bounty/hardware-wallet.md

@@ -8,12 +8,12 @@ date: '2018-05-25'
 
 Since LBRY is a fork of Bitcoin Core, integrating into existing hardware wallet platforms should be fairly straightforward. Two of the most popular hardware wallet platforms are Ledger and Trezor. You can find all the LBRY specific blockchain modifications on our [LBRYcrd GitHub repo](https://github.com/lbryio/lbrycrd) and more specifically in the [chain params code](https://github.com/lbryio/lbrycrd/blob/master/src/chainparams.cpp).
 
-The Trezor integration is a bit more involved and thus includes a 30% bonus on top of the stated bounty amount. 
+The Trezor integration is a bit more involved and thus includes a 30% bonus on top of the stated bounty amount.
-- [Ledger GitHub](https://github.com/LedgerHQ/ledger-nano-s) - Ledger Nano GitHub respository with guidelines on how to develop. This will involve setting up their SDK and creating a Chrome app. 
+- [Ledger GitHub](https://github.com/LedgerHQ/ledger-nano-s) - Ledger Nano GitHub respository with guidelines on how to develop. This will involve setting up their SDK and creating a Chrome app.
-- [Trezor GitHub](https://github.com/trezor) - Please see Trezor's [developer guide](https://doc.satoshilabs.com/trezor-tech/) for more information on integrations. 
+- [Trezor GitHub](https://github.com/trezor) - Please see Trezor's [developer guide](https://doc.satoshilabs.com/trezor-tech) for more information on integrations.
 
 Status:
-Ledger - In Progress: 
+Ledger - In Progress:
 https://github.com/LedgerHQ/ledger-live-common/pull/49
 https://github.com/LedgerHQ/blue-app-btc/pull/47
 https://github.com/LedgerHQ/lib-ledger-core/pull/24

content/bounty/lbry-binding.md

@@ -14,16 +14,16 @@ Completing this bounty involves creating a simple library to make it as easy as
 
 An example of a binding can be found in the [php-api](https://github.com/lbryio/php-api) repo and the entire listing can be found on [lbry.tech](https://lbry.tech/resources/api-wrappers).
 
-A binding can typically be written using cURL in less than 100 lines of code. The repo should be well documented for the wrapper language and have install/setup instructions and tests. 
+A binding can typically be written using cURL in less than 100 lines of code. The repo should be well documented for the wrapper language and have install/setup instructions and tests.
 
-If you are pursuing this effort, please [email us](mailto:hello@lbry.io) so we can update this bounty with the current progress. 
+If you are pursuing this effort, please [email us](mailto:hello@lbry.io) so we can update this bounty with the current progress.
 
-Bounty Status:   
+Bounty Status:
-Ruby - Completed  
+Ruby - Completed
-Lua - Completed  
+Lua - Completed
-Java - Completed  
+Java - Completed
-Javascript - Completed   
+Javascript - Completed
-Rust - Started/Claimed   
+Rust - Started/Claimed
-C++ - Completed  
+C++ - Completed
-Python - Completed   
+Python - Completed
 Dart - Completed

content/bounty/mining-inflation.md

@@ -6,15 +6,15 @@ status: completed
 date: '2018-05-25'
 ---
 
-LBRY Credits (LBC) are distributed via the mining process on the blockchain approximately every 150 seconds (2.5 minutes), also known as the block interval. There is a total supply of 1 Billion credits, of which LBRY [controls 400M](https://lbry.io/faq/credit-policy) for funding, rewarding users and partnerships. The other 600M will be mined over a period of ~20 years from inception (June 2016).
+LBRY Credits (LBC) are distributed via the mining process on the blockchain approximately every 150 seconds (2.5 minutes), also known as the block interval. There is a total supply of 1 Billion credits, of which LBRY [controls 400M](https://lbry.io/faq/credit-policy) for funding, rewarding users and partnerships. The other 600M will be mined over a period of around 20 years from inception (June 2016).
 
 The [mining schedule](https://lbry.io/faq/block-rewards) details how these credits will be distributed. We are currently in the logarithmically decreasing phase of the mining process where, at the time of this writing (May 20, 2018), the current block reward is 359 LBC. You can find the current block reward by visiting the [explorer](https://explorer.lbry.io) page and clicking the latest block to find the first output.
 
-The goal of this bounty is to analyze and visualize the impact of mining inflation on coin supply. The end result would be the calculation code and web embeddable supply chart. Click [here](https://www.bitcoinmining.com/how-are-new-bitcoins-created/) to find an example. At minimum, the x-axis should display dates and the y-axis is the cumulative LBC available.     
+The goal of this bounty is to analyze and visualize the impact of mining inflation on coin supply. The end result would be the calculation code and web embeddable supply chart. Click [here](https://www.bitcoinmining.com/how-are-new-bitcoins-created) to find an example. At minimum, the x-axis should display dates and the y-axis is the cumulative LBC available.
 
 Hints:
-- [Sample PHP Program](https://drive.google.com/open?id=19LXPIBhZnd-SEnQlrke2tb-ZwESrbK2D) to calculate estimated block reward at any given time.
+- [Sample PHP Program](https://drive.google.com/open?id=19LXPIBhZnd-SEnQlrke2tb-ZwESrbK2D) to calculate estimated block reward at any given time
-- Use actual block times from https://explorer.lbry.io (or (Chainquery)[https://github.com/lbryio/chainquery) if it's available) for historical data
+- Use actual block times from [explorer.lbry.io](https://explorer.lbry.io) (or (Chainquery)[https://github.com/lbryio/chainquery) if it's available) for historical data
 
 Bonus: Overlay with circulating supply information from CoinMarketCap.com
 

content/bounty/modified-block-explorer.md

@@ -6,7 +6,7 @@ status: complete
 date: '2016-07-01'
 ---
 
-LBRY currently maintains and runs a block explorer at [explorer.lbry.io/](https://explorer.lbry.io/).
+LBRY currently maintains and runs a block explorer at [explorer.lbry.io](https://explorer.lbry.io).
 
 This explorer is a fork of Iquidus Explorer and is [on GitHub](https://github.com/lbryio/lbry-explorer).
 
@@ -19,4 +19,4 @@ The explorer should be modified to:
 - Display claim information (name, claim txid, value, total amount, supports, and previous updates) provided a claim id
 - Display information for contesting name claims provided a lbry name
 
-This will likely require polling for changes in the result of `lbrycrd-cli getclaimsintrie` after each block, and subsequently populating values from `lbrycrd-cli getclaimsforname` and `lbrycrd-cli getclaimsfortx`. 
+This will likely require polling for changes in the result of `lbrycrd-cli getclaimsintrie` after each block, and subsequently populating values from `lbrycrd-cli getclaimsforname` and `lbrycrd-cli getclaimsfortx`.

content/bounty/publish-open-content.md

@@ -6,8 +6,7 @@ status: complete
 date: '2016-07-01'
 ---
 
-There are a large number of open content sources. Everything from public domain movies on [Internet Archive](https://archive.org/details/movies)
+There are a large number of open content sources. Everything from public domain movies on [Internet Archive](https://archive.org/details/movies) to books from [Project Gutenberg](https://www.gutenberg.org).
-to books from [Project Gutenberg](https://www.gutenberg.org/).
 
 This project is to programmatically index, download, and port this content to the LBRY network.
 

content/bounty/transaction-history.md

@@ -10,7 +10,6 @@ date: '2016-07-01'
 Add a screen showing transaction history on the LBRY Browser [`lbry-web-ui`](https://github.com/lbryio/lbry-web-ui).
 
 The screen must:
-
 - Display past outgoing and incoming transactions
 - Link to the LBRY [block explorer](https://explorer.lbry.io) for transactions
 

content/bounty/twitter-tipbot.md

@@ -6,7 +6,7 @@ status: completed
 date: '2018-02-13'
 ---
 
-This bounty is to create a tipbot that can be used to send/receive LBRY Credits(LBC) on Twitter.  
+This bounty is to create a tipbot that can be used to send/receive LBRY Credits(LBC) on Twitter.
 
 References to other LBRY tipbots:
 [Reddit tipbot](https://github.com/lbryio/lbry-social-tipbot)

content/bounty/typos-and-edits.md

@@ -12,4 +12,4 @@ This includes everything from low-level help messages or comments in code to the
 
 Please initiate a pull request on GitHub to receive this bounty.
 
-Note: Bounty award may be higher or lower depending on the nature of the change(s). 
+Note: Bounty award may be higher or lower depending on the nature of the change(s).

content/bounty/wallet-ui.md

@@ -10,7 +10,6 @@ date: '2016-07-01'
 Add a basic wallet interface to the LBRY Browser [`lbry-desktop`](https://github.com/lbryio/lbry-desktop).
 
 The interface must support:
-
 - Generating a new wallet address.
 - Sending a variable number of credits to a specified address from the active wallet.
 - Displaying an address to receive credits.

content/bounty/web-i18n.md

@@ -9,7 +9,6 @@ date: '2016-07-01'
 lbry.io already has a partial internationalization framework and some translations, but additional work is required before they can be enabled.
 
 To complete this bounty, lbry.io must be modified to:
-
 - Allow modification of your selected language in the navigation
 - Storing selected language in the user session
 - Reverse look-up your IP and choose a default language if a user has not selected one

content/credit-reports/2016-Q2.md

@@ -13,7 +13,6 @@ This is LBRY's first quarterly report. We enter with zero credits expended. We a
 ### Community Fund
 
 Currently, we are engaging in the following programs:
-
 - 3-20 LBC for users invited to participate in the beta. This program is expected to continue well throughout this quarter.
 - 1-5 LBC for referrals. This program is expected to continue in parallel with above.
 - Up to 2,000 LBC for certain publishers to join LBRY. This program is new and experimental, and is subject to revision.

content/credit-reports/2016-Q3.md

@@ -3,6 +3,7 @@ title: "Quarterly Credit Report: Third Quarter 2016"
 sheet: https://docs.google.com/spreadsheets/d/1zPG58YuLPqpB3yzypntRWouoEVc4saDOifpnvnwS8Rc/edit?ts=57f28d0e#gid=799352054
 category: policy
 ---
+
 ## Summary
 
 This is LBRY's second quarterly report. This quarter we outlaid only 267,778 of the 2,000,000 allocated Community credits. 100,000 operational credits were exchanged with Shapeshift to provide liquidity. No institutional credits were moved or spent.
@@ -16,7 +17,7 @@ This is LBRY's second quarterly report. This quarter we outlaid only 267,778 of
 - 19,150 LBRY credits outlaid to community members for completing bounties
 - 75,777 LBRY credits outlaid in Slack tips*
 
-*Some tip outlays were for bounties and to reward early people who stepped up to manage the community before we had a formal program. We have ceased using Slack tips for bounties and community management and will be able to better differentiate these moving forward.
+*Some tip outlays were for bounties and to reward early people who stepped up to manage the community before we had a formal program. We have ceased using Slack tips for bounties and community management and will be able to better differentiate these moving forward.*
 
 Over the next quarter we anticipate continued substantial use of the Community credits to grow both the user base and the publishing base. We expect these outlays to match or exceed those of this quarter, but not to dramatically exceed these outlays.
 

content/credit-reports/2016-Q4.md

@@ -1,9 +1,9 @@
-
 ---
 title: "Quarterly Credit Report: Fourth Quarter 2016"
 sheet: https://docs.google.com/spreadsheets/d/11nKwFXN3gIQHnE7jYjEK5AFClyAde9aFs6UlnGX3Uzg/edit#gid=799352054
 category: policy
 ---
+
 ## Summary
 
 This quarter we did not move any community credits from cold storage.  We spent 293,604 already moved community credits on line items detailed below. No operational credits were moved or spent.  No institutional credits were moved or spent.
@@ -13,20 +13,17 @@ As the LBRY protocol performance and reliability has increased, we anticipate in
 
 ### Community Fund
 
--Community managers received 261,109 LBRY credits this quarter
+- Community managers received 261,109 LBRY credits this quarter
-
+- Beta invitees received 22,400 LBRY credits this quarter
--Beta invitees received 22,400 LBRY credits this quarter
+- Bounty participants received 5,750 LBRY credits this quarter
-
+- 4,345 LBRY credits were used for "other" purposes, mostly given to developers
--Bounty participants received 5,750 LBRY credits this quarter
-
--4,345 LBRY credits were used for “other” purposes, mostly given to developers
 
 This quarter was a down quarter in credit outlays because we declined to send beta invites to users while the protocol was showing poor reliability.
 As reliability has been increasing, we anticipate inviting many if not all users on the beta waitlist. This will represent a significant uptick in credit outlays, possibly as much as 1-2 million LBC. We will also be launching a new program offering credits to developers.
 
 ### Operational Fund
 
--No activity this quarter
+- No activity this quarter
 
 We anticipate no usage of credits from this fund this quarter.
 

content/credit-reports/2017-Q1.md

@@ -3,6 +3,7 @@ title: "Quarterly Credit Report: First Quarter 2017"
 sheet: https://docs.google.com/spreadsheets/d/1c-8CR1ro7lKOANHhWhivF7bZ19_ppgCq-d-HD_u43vM/edit#gid=799352054
 category: policy
 ---
+
 ## Summary
 
 This quarter we moved 3 million community credits from cold storage.  We spent 1,186,244 total community credits on line items detailed below. No operational credits were moved or spent.  No institutional credits were moved or spent.

content/credit-reports/2017-Q2.md

@@ -3,6 +3,7 @@ title: "Quarterly Credit Report: Second Quarter 2017"
 sheet: https://docs.google.com/spreadsheets/d/1APKXW-JIH6Wq-pWqiDaUfj0MTRKz01QL9yIDVZU7LZI/
 category: policy
 ---
+
 ## Summary
 
 This quarter we did not move any credits from cold storage.  We spent 704,306 total community credits on line items detailed below. No operational credits were moved or spent.  No institutional credits were moved or spent.
@@ -14,17 +15,11 @@ As the LBRY protocol performance and reliability has again increased, we anticip
 
 
 Bounty 126,592 LBRY Credits
-
 Testing 62,471 LBRY Credits
-
 Invite / API 255,805 LBRY Credits
-
 Quickstart 45,000 LBRY Credits
-
 Modpay 99,800 LBRY Credits
-
 Dev Eval / Salary 62,965 LBRY Credits
-
 Other 51,673 LBRY Credits
 
 As reliability has been increasing, we anticipate inviting many, if not, all users on the beta waitlist. This will represent a significant uptick in credit outlays, possibly as much as 1-2 million LBC.

content/credit-reports/2017-Q3.md

@@ -3,6 +3,7 @@ title: "Quarterly Credit Report: Third Quarter 2017"
 sheet: https://docs.google.com/spreadsheets/d/15wm2cEVa9eQnHQVHDg7muRXm1dzFXJ6ftqEJBuNixGM/edit?usp=sharing
 category: policy
 ---
+
 ## Summary
 
 This quarter we did not move any credits from cold storage.  We spent 867,956 total community credits on line items detailed below. 1,000,000 operational credits were moved to markets.  No institutional credits were moved or spent.

content/credit-reports/2017-Q4.md

@@ -3,6 +3,7 @@ title: "Quarterly Credit Report: Fourth Quarter 2017"
 sheet: https://docs.google.com/spreadsheets/d/1MjzKv6Cr-Yj9x4dJgaHzi0YT51ib4FBje-3nPfUtQOg/edit?usp=sharing
 category: policy
 ---
+
 ## Summary
 
 This quarter we moved 5,000,000 credits from cold storage.  We spent 645,021 total community credits on line items detailed below. 5,000,000 operational credits were moved to markets to improve capitalization. No institutional credits were moved or spent.

content/credit-reports/2018-Q1.md

@@ -3,6 +3,7 @@ title: "Quarterly Credit Report: First Quarter 2018"
 sheet: https://docs.google.com/spreadsheets/d/17GIrc-cmoXEY9x3NYhtxd45g2mHnuJ7cjUy_TfmhLMA/edit?usp=sharing
 category: policy
 ---
+
 ## Summary
 This quarter we moved no credits from cold storage.  We spent 393,585 total community credits on line items detailed below. No operational credits were moved to markets. No institutional credits were moved or spent.
 We anticipate comparable or larger total outlays in Q2 2018. Operational spending may increase, but not significantly, and community spending is likely to be higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 500,000 to 3,000,000+ LBC. Additionally, LBRY has started a program for YouTubers that will scale up credit outlays. Finally, as it has now become de rigueur to state, no institutional outlays are expected, but a pilot program could happen.

content/credit-reports/2018-Q2.md

@@ -3,9 +3,10 @@ title: "Quarterly Credit Report: Second Quarter 2018"
 sheet: https://docs.google.com/spreadsheets/d/1aRmrjTNfiKQwzW5WB_tcVJzHR-UXrCz6vHpINMfTVWs/edit?usp=sharing
 category: policy
 ---
+
 ## Summary
 This quarter we moved no credits from cold storage.  We spent 738,027 total community credits on line items detailed below. No operational credits were moved to markets. No institutional credits were moved or spent.
-We anticipate comparable or larger total outlays in Q3 2018. Operational spending may increase, but not significantly, and community spending is likely to be higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 300,000 to 1,500,000+ LBC. LBRY is also likely to form it’s first institutional partnership, with spending anticipated to be around 500,000 LBC.
+We anticipate comparable or larger total outlays in Q3 2018. Operational spending may increase, but not significantly, and community spending is likely to be higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 300,000 to 1,500,000+ LBC. LBRY is also likely to form it's first institutional partnership, with spending anticipated to be around 500,000 LBC.
 
 ## Overview By Fund
 

content/credit-reports/2018-Q3.md

@@ -3,9 +3,10 @@ title: "Quarterly Credit Report: Third Quarter 2018"
 sheet: https://docs.google.com/spreadsheets/d/1SqRGHtfZ7-gokvaHk8w3_72aD9zR98Sf345tGX-a7K0/edit?usp=sharing
 category: policy
 ---
+
 ## Summary
 This quarter we moved no credits from cold storage.  We spent 958,201 total community credits on line items detailed below. Under 50,000 operational credits were used for the LBRY employee LBC purchase program. 100,000 institutional credits were spent from the institutional fund as part of a new partnership with a media organization.
-We anticipate comparable or larger total outlays in Q4 2018. Operational spending may increase, but not significantly, and community spending is likely to be higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 300,000 to 1,500,000+ LBC. It is also possible that LBRY will continue to explore usage of it’s institutional fund.
+We anticipate comparable or larger total outlays in Q4 2018. Operational spending may increase, but not significantly, and community spending is likely to be higher. We will continue to incentivize new users and other beneficial behavior, which is likely to involve 300,000 to 1,500,000+ LBC. It is also possible that LBRY will continue to explore usage of it's institutional fund.
 
 ## Overview By Fund
 

content/faq/ARCHIVE-contributing.mdARCHIVE

@@ -1,6 +1,6 @@
----	
+---
-title: Contributing to LBRY	
+title: Contributing to LBRY
-category: other	
+category: other
 ---
 
 This Document now lives at https://lbry.tech/contribute

content/faq/ARCHIVE-development-status..archive

@@ -1,9 +1,10 @@
 ---
-title: What is LBRY’s development status right now? Plans for the future?
+title: What is LBRY's development status right now? Plans for the future?
 category: developer
 ---
-LBRY is currently in invite-only beta, with desktop apps for Linux, MacOS, and a pre-release version of Windows. There are approximately 5K active users and hundreds of content creators. The network already hosts big-name content like the [feature film *It’s A Disaster*](https://lbry.io/news/launch-a-disaster) and videos from [Adult Swim’s MillionDollarExtreme](https://lbry.io/news/mde-on-lbry). We announce new featured content every Thursday on our [blog](https://lbry.io/news), [Twitter](https://twitter.com/lbryio), and [Facebook](https://www.facebook.com/lbryio).
 
-The waitlist to get into the beta is ~150K people long. This shocks even us, and we’re racing to get the user experience and backend technologies to a level where we’re comfortable opening the beta to everyone. The target for open beta is this winter. Mushy target, we know, but these things are hard to time.
+LBRY is currently in invite-only beta, with desktop apps for Linux, MacOS, and a pre-release version of Windows. There are approximately 5K active users and hundreds of content creators. The network already hosts big-name content like the [feature film *It's A Disaster*](https://lbry.io/news/launch-a-disaster) and videos from [Adult Swim's MillionDollarExtreme](https://lbry.io/news/mde-on-lbry). We announce new featured content every Thursday on our [blog](https://lbry.io/news), [Twitter](https://twitter.com/lbryio), and [Facebook](https://www.facebook.com/lbryio).
 
-In the meantime, we could use your encouragement. This is a difficult project that cannot succeed without people demonstrating they want an alternative to Silicon Valley megacorp media services. So [join the beta](https://lbry.io/get), [share our blog posts](https://lbry.io/news), and [join our subreddit /r/lbry](https://www.reddit.com/r/lbry/). Your excitement is like Red Bull to our weary coders!
+The waitlist to get into the beta is ~150K people long. This shocks even us, and we're racing to get the user experience and backend technologies to a level where we're comfortable opening the beta to everyone. The target for open beta is this winter. Mushy target, we know, but these things are hard to time.
+
+In the meantime, we could use your encouragement. This is a difficult project that cannot succeed without people demonstrating they want an alternative to Silicon Valley megacorp media services. So [join the beta](https://lbry.io/get), [share our blog posts](https://lbry.io/news), and [join our subreddit /r/lbry](https://www.reddit.com/r/lbry). Your excitement is like Red Bull to our weary coders!

content/faq/ARCHIVED-claimtrie-implementation.archive

@@ -1,79 +1,79 @@
 ---
 title: The ClaimTrie Implementation in LBRY
-category: developer 
+category: developer
 ---
 
-## Introduction 
+## Introduction
 
-This document describes the implementation detail of the ClaimTrie in LBRY. The ClaimTrie is the data structure which LBRY uses to store claims to names. It uses a [Trie](https://en.wikipedia.org/wiki/Trie) to efficiently store all claimed names, which can then be hashed the same way a [Merkle Tree](https://en.wikipedia.org/wiki/Merkle_tree) is hashed. The root hash of the ClaimTrie is stored in the blockheader of each LBRY block, enabling nodes in the LBRY network to efficiently and securely validate the state of the ClaimTrie.   
+This document describes the implementation detail of the ClaimTrie in LBRY. The ClaimTrie is the data structure which LBRY uses to store claims to names. It uses a [Trie](https://en.wikipedia.org/wiki/Trie) to efficiently store all claimed names, which can then be hashed the same way a [Merkle Tree](https://en.wikipedia.org/wiki/Merkle_tree) is hashed. The root hash of the ClaimTrie is stored in the blockheader of each LBRY block, enabling nodes in the LBRY network to efficiently and securely validate the state of the ClaimTrie.
 
 Bids to claim a name must win out against other claims for the same name before they can be inserted into the ClaimTrie. The short summary is that the bid with the most LBRY credits assigned to it will win the right to claim a name, but the implementation detail is more involved and, this is what we aim to cover in this document. Bids to claim a name have four properties tied to it :
- 
+
 1. *Name* : The name is a human-readable address and is the property that the bids compete to obtain.
-2. *Value* : The value is the data that is attached to the name. 
+2. *Value* : The value is the data that is attached to the name.
-3. *Quantity* : The quantity is the number of LBRY credits assigned to the bid. 
+3. *Quantity* : The quantity is the number of LBRY credits assigned to the bid.
-4. *Claim Id* : A unique ID used to identify the bid. 
+4. *Claim Id* : A unique ID used to identify the bid.
 
 There are also three different bid types: claim, update, and support.
 
 1. *Claim*: A claim represent new bids for a name. If a user wants to make a claim to a brand new name, or submit a competing claim to an existing name, this bid type is used.
-2. *Support*: A support adds to the total quantity of credits assigned to any bid by referring to a bid's Claim Id. A support bid can be made by anyone on any bid. It does not have its own Value or its own Claim Id, but it does contain the Claim Id of the bid that it is supporting. 
+2. *Support*: A support adds to the total quantity of credits assigned to any bid by referring to a bid's Claim Id. A support bid can be made by anyone on any bid. It does not have its own Value or its own Claim Id, but it does contain the Claim Id of the bid that it is supporting.
-3. *Update*:  An update can modify the value and the quantity for a pre-existing claim without changing the Claim Id or the name that it is bidding on. Since the Claim Id of the original bid is not changed, an updated bid will still retain all the supports attached to the original bid. 
+3. *Update*:  An update can modify the value and the quantity for a pre-existing claim without changing the Claim Id or the name that it is bidding on. Since the Claim Id of the original bid is not changed, an updated bid will still retain all the supports attached to the original bid.
 
 
 ## ClaimTrie Bid States
 
-This section describes how bids are processed by the ClaimTrie in order to determine which bids have won the rights to claim a particular name.  There are 6 states a bid can be in, and they are explained below.  
+This section describes how bids are processed by the ClaimTrie in order to determine which bids have won the rights to claim a particular name.  There are 6 states a bid can be in, and they are explained below.
 
 1. *Not accepted*: This bid is in a transaction which has not yet been included in a block which has been included in the blockchain.
 2. *Accepted*: This bid has been accepted into the blockchain. This happens when the transaction containing the TXout which contains the bid is included in a block which is included in the blockchain.
-3. *Active*: This bid is capable of controlling a name. Active bids must be in the “accepted” state and not “expired” or “spent”. Bids are “active” when either of the two conditions below is met:
+3. *Active*: This bid is capable of controlling a name. Active bids must be in the "accepted" state and not "expired" or "spent". Bids are "active" when either of the two conditions below is met:
     * The current block height exceeds the height of the block at which the bid became accepted plus the activation delay for the name as calculated at either the block at which the bid was accepted or any block after the bid was accepted. The activation delay is calculated as follows:
-      * If, immediately before this block was included in the blockchain, there were no ‘active’ bids for the name and therefore no ‘controlling’ bids, the delay is 0.
+      * If, immediately before this block was included in the blockchain, there were no 'active' bids for the name and therefore no 'controlling' bids, the delay is 0.
-      * If there is a “controlling” bid for the name: Delay = (HeightB - HeightA) / 32
+      * If there is a "controlling" bid for the name: Delay = (HeightB - HeightA) / 32
         * HeightA = the most recent height at which the bid controlling the name changed
         * HeightB = the current height
         * Maximum delay is 7 days of blocks at 2.5 min/block (or 4032 blocks). Thus maximum delay can be reached in 224 (7x32) days.
-    * The bid’s Claim Id matches the Claim Id of the bid which was the controlling bid immediately before the block containing this bid was included in the blockchain. In other words, it is either an update to the previous controlling bid or update to update to the previous controlling bid if the bid was updated twice in this block, etc.
+    * The bid's Claim Id matches the Claim Id of the bid which was the controlling bid immediately before the block containing this bid was included in the blockchain. In other words, it is either an update to the previous controlling bid or update to update to the previous controlling bid if the bid was updated twice in this block, etc.
 
-4. *Controlling*: This bid currently controls the name. When clients ask which bid controls the name as of the current block, this is the bid that will be returned. Must be in the “active” state and only one bid for any name may be in this state. A support cannot be in the “controlling” state. To determine which “active” bid is the “controlling” bid for each name:
+4. *Controlling*: This bid currently controls the name. When clients ask which bid controls the name as of the current block, this is the bid that will be returned. Must be in the "active" state and only one bid for any name may be in this state. A support cannot be in the "controlling" state. To determine which "active" bid is the "controlling" bid for each name:
-    * Add the quantity of each ‘active’ bid to the quantity of all ‘active’ supports for that bid, and take whichever is greatest. If two bids have the same quantity, older bids take precedence over newer bids.	
+    * Add the quantity of each 'active' bid to the quantity of all 'active' supports for that bid, and take whichever is greatest. If two bids have the same quantity, older bids take precedence over newer bids.
-    * If the bid with the greatest amount does not have the same claimID as the bid which was ‘controlling’ prior to including the current block, change the delay for the name as of the current block to 0, redetermine which bids and supports should be active, and then perform the previous calculation again.
+    * If the bid with the greatest amount does not have the same claimID as the bid which was 'controlling' prior to including the current block, change the delay for the name as of the current block to 0, redetermine which bids and supports should be active, and then perform the previous calculation again.
-    * At this point, the bid calculated to have the greatest amount behind it is the ‘controlling’ bid as of this block
+    * At this point, the bid calculated to have the greatest amount behind it is the 'controlling' bid as of this block
-5. *Spent*: A transaction has been included in the blockchain which spends the TXout which contains the bid. Must be in the ‘accepted’ state.
+5. *Spent*: A transaction has been included in the blockchain which spends the TXout which contains the bid. Must be in the 'accepted' state.
-6. *Expired*: All bids ‘expire’ regardless of what state they are in when the current block height exceeds the height of the block at which the bid was accepted plus 52416 blocks, or 91 days ( currently this is set to 262974 blocks, or 456 days, which will be fixed in a future hard fork ). Updated claims will restart the expiration timer at the block height of the update.  
+6. *Expired*: All bids 'expire' regardless of what state they are in when the current block height exceeds the height of the block at which the bid was accepted plus 52416 blocks, or 91 days ( currently this is set to 262974 blocks, or 456 days, which will be fixed in a future hard fork ). Updated claims will restart the expiration timer at the block height of the update.
 
 
-## ClaimTrie Transaction Implementation 
+## ClaimTrie Transaction Implementation
 
 This section describes how the three ClaimTrie bid types are implemented as transactions on the blockchain. Readers should have prior knowledge of Bitcoin [transactions](https://en.bitcoin.it/wiki/Transaction) and the Bitcoin [scripting system](https://en.bitcoin.it/wiki/Script).  LBRY supports three op codes that do not exist in Bitcoin: OP_CLAIM_NAME, OP_SUPPORT_CLAIM, and OP_UPDATE_CLAIM (in Bitcoin they are respectively OP_NOP6, OP_NOP7, and OP_NOP8). Each op code will push a zero on to the execution stack, and in addition, will trigger the ClaimTrie to perform calculations necessary for each bid type. Below are the three supported transactions scripts using these op codes.
 
 ```python
-OP_CLAIM_NAME <Name> <Value> OP_2DROP OP_DROP [script pubkey] 
+OP_CLAIM_NAME <Name> <Value> OP_2DROP OP_DROP [script pubkey]
-OP_UPDATE_CLAIM <Name> <ClaimId> <Value> OP_2DROP OP_2DROP [script pubkey]  
+OP_UPDATE_CLAIM <Name> <ClaimId> <Value> OP_2DROP OP_2DROP [script pubkey]
 OP_SUPPORT_CLAIM <Name> <ClaimId> OP_2DROP OP_DROP [script pubkey]
 ```
-[script pubkey] can be any valid Bitcoin payout script, thus it can be something like a standard “pay to pubkey” script to a user controlled address. Also note that the zero pushed onto the stack by the ClaimTrie op codes, and the ClaimTrie vectors, are all dropped by the preceding OP_2DROP and OP_DROP. This means that ClaimTrie transactions exist as prefixes to Bitcoin payout scripts and can be spent in the same way as is expected in Bitcoin. 
+[script pubkey] can be any valid Bitcoin payout script, thus it can be something like a standard "pay to pubkey" script to a user controlled address. Also note that the zero pushed onto the stack by the ClaimTrie op codes, and the ClaimTrie vectors, are all dropped by the preceding OP_2DROP and OP_DROP. This means that ClaimTrie transactions exist as prefixes to Bitcoin payout scripts and can be spent in the same way as is expected in Bitcoin.
 
-For example, a claim transaction using a pay to pubkey script will have the below full payout script. Let's also say that this claim is for the name “Fruit” to be set to value “Apple”. 
+For example, a claim transaction using a pay to pubkey script will have the below full payout script. Let's also say that this claim is for the name "Fruit" to be set to value "Apple".
 
 ```python
 OP_CLAIM_NAME <Fruit> <Apple> OP_2DROP OP_DROP OP_DUP OP_HASH160 <LBRY_Address_A> OP_EQUALVERIFY OP_CHECKSIG
 ```
 
-Like any standard Bitcoin transaction output script, it will be associated with a transaction hash and a transaction output index. The transaction hash and transaction output index is concatenated and hashed using RIPEMD-160 to create the Claim Id for this claim. For the example above, let's say it has a Claim Id X. A support for this bid will have the below full payout script.  
+Like any standard Bitcoin transaction output script, it will be associated with a transaction hash and a transaction output index. The transaction hash and transaction output index is concatenated and hashed using RIPEMD-160 to create the Claim Id for this claim. For the example above, let's say it has a Claim Id X. A support for this bid will have the below full payout script.
 
 ```python
 OP_SUPPORT_CLAIM <Fruit> <X> OP_2DROP OP_DROP OP_DUP OP_HASH160 <LBRY_Address_B> OP_EQUALVERIFY OP_CHECKSIG
 ```
 
-And now let's say we want to update the original claim to change the value to “Banana”. An update transaction has a special requirement that it must spend the existing claim that it wishes to update in its redeem script. Otherwise, it will be considered invalid and will not make it into the ClaimTrie. Thus it will have the below redeem script to spend the claim created to set name “Fruit” to “Apple”. Note that this is identical to the standard way of redeeming a “pay to pubkey” script in Bitcoin.
+And now let's say we want to update the original claim to change the value to "Banana". An update transaction has a special requirement that it must spend the existing claim that it wishes to update in its redeem script. Otherwise, it will be considered invalid and will not make it into the ClaimTrie. Thus it will have the below redeem script to spend the claim created to set name "Fruit" to "Apple". Note that this is identical to the standard way of redeeming a "pay to pubkey" script in Bitcoin.
 
 ```python
 <Signature> <Public_key_for_LBRY_Address_A>
 ```
 
-And the payout script for the update transaction is below. 
+And the payout script for the update transaction is below.
 
 ```python
 OP_UPDATE_CLAIM <Fruit> <X> <Banana> OP_2DROP OP_2DROP OP_DUP OP_HASH160 <LBRY_Address_C> OP_EQUALVERIFY OP_CHECKSIG

content/faq/ARCHIVED-how-to-encrypt-wallet.archive

@@ -2,6 +2,7 @@
 title: How do I encrypt my wallet?
 category: wallet
 ---
+
 **THIS FAQ WAS MOVED TO LBRY.TECH ***
 
 *Note: The below instructions are the [LBRYCrd Full Blockchain wallet](https://github.com/lbryio/lbrycrd) and not the default wallet that ships with the LBRY App. We are still working on an encryption solution for this.*

content/faq/ARCHIVED-how-to-run-lbry-with-lbrycrdd.archive

@@ -2,6 +2,7 @@
 title:  How do I run LBRY with lbrycrdd?
 category: mining
 ---
+
 ***WARNING: Currently, the LBRY app does not support the LBRYcrd wallet, but this functionality may be available in the future***
 
 Start LBRY with the `--wallet` flag set:

content/faq/ARCHIVED-proof-algorithm.archive

@@ -17,7 +17,7 @@ right = ripemd(intermediate[len(intermediate)/2:]) # and the right half
 proof = sha256(sha256(left + right))  # concatenate the two halves, and double-sha256() it again
 ```
 
-For comparison, Bitcoin's algorithm is 
+For comparison, Bitcoin's algorithm is
 
 ```python
 proof = sha256(sha256(data))

content/faq/ARCHIVED-to-log-to-console.archive

@@ -3,4 +3,4 @@ title: How can I see the log in the terminal?
 category: developer
 ---
 
-Simply run `lbry`, or the daemon `lbrynet-daemon`, in a terminal. 
+Simply run `lbry`, or the daemon `lbrynet-daemon`, in a terminal.

content/faq/ARCHIVEhow-do-i-check-my-lbc-address.archive

@@ -5,20 +5,20 @@ category: wallet
 
 ## Using lbrynet (the usual way)
 
-To get your current, unused address 
+To get your current, unused address
 
     lbrynet-cli wallet_unused_address
 
-To create a new address 
+To create a new address
 
     lbrynet-cli wallet_new_address
 
 To list all addresses in your wallet
 
     lbrynet-cli wallet_list
-    
+
-To get your balance 
+To get your balance
-    
+
     lbrynet-cli wallet_balance
 
 ## Using lbrycrd (the old way)

content/faq/acceptable-use-policy.md

@@ -37,6 +37,6 @@ If you are a developer, you will need to complete the verification process befor
 
 As a statement of principle, you are encouraged to associate your project, product, service, domain, or company name with LBRY, so long as you're a credit to the community.
 
-You should not do anything that causes confusion regarding roles. You can describe your company as “Top Shelf Consulting, providers of LBRY development,” but not “The LBRY Development Group.” Registering a domain that could be mistaken for part of LBRY's infrastructure would also be inappropriate.
+You should not do anything that causes confusion regarding roles. You can describe your company as "Top Shelf Consulting, providers of LBRY development," but not "The LBRY Development Group." Registering a domain that could be mistaken for part of LBRY's infrastructure would also be inappropriate.
 
 If you are not sure if your use is within bounds or not, please [come talk with us](https://chat.lbry.io) about it. We know we can only envision some of the innovation that will happen on the LBRY network and would hate to miss a great opportunity for confusion in this area.

content/faq/android-basics.md

@@ -1,14 +1,12 @@
 ---
-
 title: LBRY Android App Basics
 category: getstarted
 order: 2
-
 ---
 
 The LBRY Browser for Android allows you to view free and paid content via the Explore and Trending sections, search for content on LBRY,  send/receive LBRY Credits (LBC) and earn credits through LBRY Rewards.
 
-The app runs on top of the [LBRY protocol](https://lbry.io/faq/what-is-lbry) which is a peer-to-peer (P2P), decentralized file sharing and payment network secured by blockchain technology. 
+The app runs on top of the [LBRY protocol](https://lbry.io/faq/what-is-lbry) which is a peer-to-peer (P2P), decentralized file sharing and payment network secured by blockchain technology.
 
 The purpose of this FAQ is to answer questions about some of the basic functionality available in the LBRY Android App. Please see our [other FAQ entries](https://lbry.io/faq) for additional information.
 
@@ -28,7 +26,7 @@ If you sign into a new email and need to transfer your verification status, you'
 
 If you want to run the LBRY app on multiple PCs or on other platforms like Android, you can sign in with the same email on all devices. Each installation will still have its separate wallet and download data (as mentioned above).
 
-Any rewards earned will be sent locally to the wallet where they are claimed. In the future, our goal to enable an opt-in wallet syncing service across devices. 
+Any rewards earned will be sent locally to the wallet where they are claimed. In the future, our goal to enable an opt-in wallet syncing service across devices.
 
 ### What Are LBRY Rewards? {#rewards}
 
@@ -38,7 +36,7 @@ In order to be eligible for Rewards, you need to verify your identity [phone num
 
 ### What Is a Wallet And How Do I Find It? {#wallet}
 
-A wallet is a secure digital file used to store, send and receive cryptocurrencies like LBRY Credits (LBC). 
+A wallet is a secure digital file used to store, send and receive cryptocurrencies like LBRY Credits (LBC).
 The LBRY Android App comes with its own wallet and is stored locally on your phone and nowhere else!
 
 **It is critical that you [backup your wallet data](https://lbry.io/faq/how-to-backup-wallet#android) in case you lose access to your phone or need to [migrate](https://lbry.io/faq/backup-data) to a new one.**
@@ -51,8 +49,8 @@ To find your wallet in the LBRY Android app, click on the 3 horizontal bars at t
 
 ![balance](https://spee.ch/e7f125b643e30f8bac2d8c4657bc14874a60e25e/WALLETADD1.jpg)
 
-### Where Do I Find My Recent Transactions?
+### Where Do I Find my Recent Transactions
-Scroll down in the Wallet menu to find recent transactions, or click `View All` to see anything older than 7 days. 
+Scroll down in the Wallet menu to find recent transactions, or click `View All` to see anything older than 7 days.
 
 ![Recent tx](https://spee.ch/daa89fcca6411ad2505cdc6e092fcaf4f22f4802/recent1.jpg)
 
@@ -66,7 +64,7 @@ Claim related [wallet transactions](https://lbry.io/faq/transaction-types) ensur
 
 ![bagdeicon](https://spee.ch/4176685c4fd51d31f623430d6ac17e9949ecab39/badge.jpg)
 
-2. After clicking on the video to play/download, the reward should be claimed automatically. If not, go into the Menu > Rewards and you will see the LBRY cast reward on the first. Tap the round circle to claim your reward. 
+2. After clicking on the video to play/download, the reward should be claimed automatically. If not, go into the Menu > Rewards and you will see the LBRY cast reward on the first. Tap the round circle to claim your reward.
 
 ![walleticon](https://spee.ch/beceef63dbf682cd1ed1ebdbee9b1845de10959b/swipe.gif)
 
@@ -99,7 +97,8 @@ Click on the bin icon and confirm deletion if you still want to delete the conte
 ![delete](https://spee.ch/7411547d0aea6da1b0c765151c4ffd0e30b2c9fd/delete1.jpg)
 
 Right after the content is deleted, you should see the same content showing on the app screen, if you click on it, it will start the download again.
-To delete additional content, please follow the same steps until you delete all the contents you do not need on your phone. We'll be improving this to allow for easier deletion multiple content at the same time. 
+
+To delete additional content, please follow the same steps until you delete all the contents you do not need on your phone. We'll be improving this to allow for easier deletion multiple content at the same time.
 
 ### How Do I Enable Background Media Playback? {#backgroundmediaplayback}
 

content/faq/archived-regtest-setup-guide.archive

@@ -22,7 +22,7 @@ To enter the environment, run:
 
 ### lbrycrd
 
-You need to download a build of `lbrycrd` from [here](https://github.com/lbryio/lbrycrd/releases/), no installation required. To configure `lbrycrd` you need to create a file at `~/.lbrycrd/lbrycrd.conf`,
+You need to download a build of `lbrycrd` from [here](https://github.com/lbryio/lbrycrd/releases), no installation required. To configure `lbrycrd` you need to create a file at `~/.lbrycrd/lbrycrd.conf`,
 containing the following.
 ```ini
 rpcuser=test

content/faq/benefit-consumers.md

@@ -3,9 +3,10 @@ title: How does LBRY benefit content consumers? Why should I bother caring?
 category: LBRY 101
 order: 2
 ---
-Do you watch YouTube? Imagine paying a few cents to eliminate all ads. 100% of the payment will go directly to the content creator – and they’ll still be earning more than YouTube offers, so they’ll want to make even more of the content you love.
 
-Do you use BitTorrent? Imagine getting paid to seed files into the network. Because there is a marketplace for these files, you can finally find rare songs and films that can’t support a torrent swarm based on popularity alone.
+Do you watch YouTube? Imagine paying a few cents to eliminate all ads. 100% of the payment will go directly to the content creator – and they'll still be earning more than YouTube offers, so they'll want to make even more of the content you love.
+
+Do you use BitTorrent? Imagine getting paid to seed files into the network. Because there is a marketplace for these files, you can finally find rare songs and films that can't support a torrent swarm based on popularity alone.
 
 Do you shop on the iTunes Store? Imagine paying less for songs, TV episodes, and music videos while having 100% of the cost go directly to the creators.
 

content/faq/block-rewards.md

@@ -17,7 +17,7 @@ The source code, and not this file, is the only true definition of the block rew
 
 ## Mining Reward Schedule
 
-Eventually 1,083,202,000<sup>1</sup> LBRY credits will exist.   
+Eventually 1,083,202,000<sup>1</sup> LBRY credits will exist.
 
 <sup>1</sup>This value was [updated from 1B](https://github.com/lbryio/lbry.io/commit/4b4a8401d8ada40203d2bfb232066f42c4ac7a84) (which was a nice round number for a FAQ) on 09/21/2018 with the goal of increasing accuracy and transparency. [View the calculation here to verify](https://www.onlinegdb.com/r1NQOiyYQ) the source code referenced above.
 

content/faq/community-top-bid.md

@@ -6,11 +6,11 @@ order: 3
 
 ### What are Community Top Bids?
 
-Community Top Bids is a public space on the LBRY application that allows for community controlled content. 
+Community Top Bids is a public space on the LBRY application that allows for community controlled content.
 
-In this area, the LBRY URLs `lbry://one` through `lbry://ten` are displayed. 
+In this area, the LBRY URLs `lbry://one` through `lbry://ten` are displayed.
 
-Anyone can share their content with the rest of the LBRY community by issuing a winning claim for one of these URLs. This mechanism enables users to promote their content and via the LBRY naming system. 
+Anyone can share their content with the rest of the LBRY community by issuing a winning claim for one of these URLs. This mechanism enables users to promote their content and via the LBRY naming system.
 
 Note that when claiming one of these URLs, no LBC is ever lost or destroyed (absent a very small transaction fee).
 
@@ -25,4 +25,4 @@ For more details on how naming works, please see: [Naming](https://lbry.io/faq/n
 
 ### How do I know if my content is overtaken?
 
-We do not have a mechanism in place to notify users when they are outbid, but one is planned for a future release. For now, you can monitor the Community Top Bids section to see if your content is still available. 
+We do not have a mechanism in place to notify users when they are outbid, but one is planned for a future release. For now, you can monitor the Community Top Bids section to see if your content is still available.

content/faq/content.md

@@ -3,21 +3,21 @@ title: How does LBRY handle content and what am I allowed to upload?
 category: publisher
 ---
 
-This guide provides answers to questions regarding what you may upload to the LBRY app and network and how it differs from current centralized/status quo systems. To learn more about reporting infringing or illegal content and DMCA procedures, please see our [DMCA article](https://lbry.io/faq/dmca). 
+This guide provides answers to questions regarding what you may upload to the LBRY app and network and how it differs from current centralized/status quo systems. To learn more about reporting infringing or illegal content and DMCA procedures, please see our [DMCA article](https://lbry.io/faq/dmca).
 
 ### What content can I legally upload to LBRY?
 
 You may upload legal content that you own or have obtained permission to use, as long as it does not infringe on the rights of others.
 This includes Public Domain content, Creative Commons or Open Source content shared according to the license requirements, and Copyrighted content where you have permission from the owner.
 
-### Because LBRY is decentralized, doesn't this mean the content can’t be removed?
+### Because LBRY is decentralized, doesn't this mean the content can't be removed?
 
-It is important to make a distinction between the LBRY protocol and any applications running on top when referring to censorship and the ability to block access to certain content. The LBRY protocol is fully decentralized and censorship-resistant - it provides permissionless access to [claiming of URLs](https://lbry.io/faq/naming) and indexing metadata on the blockchain, and facilitates data transfers over a peer to peer (P2P) network which consists of our own content severs and anyone running the LBRY protocol. This means infringing content may be stored on our servers, by the uploader and by anyone else who may have downloaded it.  
+It is important to make a distinction between the LBRY protocol and any applications running on top when referring to censorship and the ability to block access to certain content. The LBRY protocol is fully decentralized and censorship-resistant - it provides permissionless access to [claiming of URLs](https://lbry.io/faq/naming) and indexing metadata on the blockchain, and facilitates data transfers over a peer to peer (P2P) network which consists of our own content severs and anyone running the LBRY protocol. This means infringing content may be stored on our servers, by the uploader and by anyone else who may have downloaded it.
 
-On the other hand, LBRY also makes an App and other services like [spee.ch](https://spee.ch) to demonstrate the protocol's capabilities. Within our app, we will engage in non-arbitrary censorship, meaning only horrific or infringing content will be blocked and removed from our content servers. As a U.S. company, LBRY Inc. and management of our app, and other services in our control, will follow all U.S. laws, including the CDA and DMCA. If someone made an app or website using the LBRY protocol in some other country, it would have to follow that country's laws, which aren’t necessarily the same as ours. Either app would read the same blockchain though. 
+On the other hand, LBRY also makes an App and other services like [spee.ch](https://spee.ch) to demonstrate the protocol's capabilities. Within our app, we will engage in non-arbitrary censorship, meaning only horrific or infringing content will be blocked and removed from our content servers. As a U.S. company, LBRY Inc. and management of our app, and other services in our control, will follow all U.S. laws, including the CDA and DMCA. If someone made an app or website using the LBRY protocol in some other country, it would have to follow that country's laws, which aren't necessarily the same as ours. Either app would read the same blockchain though.
 
 LBRY Inc., makes no guarantee your content will be hosted on the network. The peer-to-peer network relies on seeders to host content. If no user continues to host data - including you, it will not continue to be available on the network.
 
-### What do I do if I see content that’s illegal or infringing in the LBRY App?
+### What do I do if I see content that's illegal or infringing in the LBRY App?
 
 Please read our [DMCA FAQ](https://lbry.io/faq/dmca) for more information on reporting infringing content.

content/faq/contest-t-and-cs.md

@@ -19,7 +19,7 @@ category: other
 * The winner will be notified either via social media or email within 5 days of the closing date. If the winner cannot be contacted or does not claim the prize within 48 hours of notification, we reserve the right to withdraw the prize from the winner and pick a replacement winner.
 * All winners must be at least 18 years of age.
 * The promoter will notify the winner when and where the prize can be collected. All prizes will be sent at the end of the competition. For competitions that run multiple stages, the prize will be sent at the end of the final stage.
-* The promoter’s decision in respect of all matters to do with the competition will be final and no correspondence will be entered into.
+* The promoter's decision in respect of all matters to do with the competition will be final and no correspondence will be entered into.
 * The competition and these terms and conditions will be governed by US law, and any disputes will be subject to the exclusive jurisdiction of the courts of the State of New Hampshire.
 * The winner agrees to the use of his/her name, image, comments or any other information provided in any publicity material.
 * This promotion is in no way sponsored, endorsed or administered by, or associated with, Facebook, Twitter or any other Social Network. You are providing your information to LBRY and not to any other party.

content/faq/different-alexandria.md

@@ -2,7 +2,8 @@
 title: How is LBRY different from Decent / SingularDTV / Alexandria?
 category: differences
 ---
-The first and biggest difference is that LBRY exists and has significant traction. As of this writing, Alexandria is the only one of these to release a client to the public, and there hasn’t been much progress since that release.
+
+The first and biggest difference is that LBRY exists and has significant traction. As of this writing, Alexandria is the only one of these to release a client to the public, and there hasn't been much progress since that release.
 
 It's difficult to compare LBRY to something that doesn't exist yet, but as we understand it, no alternative is providing a human-friendly namespace and discovery mechanisms like LBRY.
 

content/faq/different-ipfs.md

@@ -2,6 +2,7 @@
 title: How is LBRY different from IPFS / BitTorrent?
 category: differences
 ---
+
 IPFS and BitTorrent are wonderful technologies from which LBRY has drawn a lot of inspiration. However, they both suffer from the same flaws:
 
 - Lack of discovery. BitTorrent and IPFS provide decentralized ways to access a unique piece of data or information, but they do not provide an overall catalog that lists all of the available data or information to consume.

content/faq/different-storj.md

@@ -2,6 +2,7 @@
 title: How is LBRY different from MaidSafe / Storj?
 category: differences
 ---
+
 MaidSafe and Storj are attempting to be decentralized platforms that enable many uses, rather than a decentralized protocol designed to serve a singular purpose.
 
 LBRY is designed to do one thing and only one thing well: the discovery, access, and (optionally) purchase of digital content.

content/faq/different-toaster.md

@@ -2,11 +2,12 @@
 title: How is LBRY different from a toaster?
 category: differences
 ---
+
 Toasters transfer heat via radiative EM waves in the infrared spectrum to brown bread and make people happy.
 
 LBRY transfers data via EM waves in the infrared spectrum* to deliver content and make people happy.
 
-LBRY is also brave and little. So we’re basically, fundamentally the same as a toaster.
+LBRY is also brave and little. So we're basically, fundamentally the same as a toaster.
 
 \**Assumes fiber-optic transmission.*
 

content/faq/different-youtube.md

@@ -2,6 +2,7 @@
 title: How is LBRY different from YouTube / Netflix / Apple TV?
 category: differences
 ---
+
 YouTube, Netflix, Apple TV, and other similar services are centralized platforms controlled by a single corporate entity. These companies have the ability to change the rules unilaterally, as well as censor content to appease authoritarian governments or corporate partners.
 
 LBRY is a decentralized, open-source protocol that is controlled by its users. LBRY facilitates a similar experience to the aforementioned services but does it in a way that is entirely decentralized. LBRY can never unilaterally change the rules on publishers or consumers, making it dramatically more trustworthy.

content/faq/dmca.md

@@ -2,6 +2,7 @@
 title: DMCA takedown requests
 category: other
 ---
+
 Please see our [Content FAQ](https://lbry.io/faq/content) for an explanation of how the LBRY network handles content and how to report infringing material.
 
 ### What is a DMCA request or takedown notice?
@@ -18,7 +19,7 @@ Open the LBRY App and navigate to the content you wish to report. Underneath the
 
 Upon receipt of a DMCA request from the content owner or legal representative, LBRY Inc. will use its best judgment to determine validity. We will block access to content deemed infringing in any LBRY Inc. owned applications. LBRY Inc. will also remove any data related to the infringing content from servers within its control.
 
-Due to the immutable nature of the LBRY blockchain, a record and metadata of the infringing content may continue to exist on network hosts if the original publisher does not remove it. The data may still exist on the original publisher's computer (and anyone who may have downloaded it prior to it being blocked) but will not be accessible through any LBRY Inc. controlled applications.  
+Due to the immutable nature of the LBRY blockchain, a record and metadata of the infringing content may continue to exist on network hosts if the original publisher does not remove it. The data may still exist on the original publisher's computer (and anyone who may have downloaded it prior to it being blocked) but will not be accessible through any LBRY Inc. controlled applications.
 
 ### Where are DMCA requests recorded?
 
@@ -26,4 +27,4 @@ You can view all of the DMCA requests LBRY receives on our [DMCA GitHub Reposito
 
 ### Can I dispute a DMCA complaint?
 
-Yes, you may. We can't give you legal advice, so check with your local attorney or legal group about how to do this. There are also good resources online to learn about DMCA counter-notices. The [EFF has published an excellent guide](https://www.eff.org/issues/intellectual-property/guide-to-youtube-removals) about how to deal with legal issues facing online content creators. If you have done the research or feel the content was blocked mistakenly, [please reach out to us](mailto:help@lbry.io). 
+Yes, you may. We can't give you legal advice, so check with your local attorney or legal group about how to do this. There are also good resources online to learn about DMCA counter-notices. The [EFF has published an excellent guide](https://www.eff.org/issues/intellectual-property/guide-to-youtube-removals) about how to deal with legal issues facing online content creators. If you have done the research or feel the content was blocked mistakenly, [please reach out to us](mailto:help@lbry.io).

content/faq/earn-credits.md

@@ -8,11 +8,9 @@ Currently, there are several ways to earn LBRY Credits, or LBC.
 
 1. LBRY users receive an LBC gift by way of in-app [rewards](https://lbry.io/faq/rewards).
 1. LBRY users get LBC for [referring](https://lbry.io/faq/referrals) other users via the LBRY app (see Invites section of the wallet).
-1. You can earn LBC for helping with various tasks. Talk to us on [Discord Chat](https://chat.lbry.io/) if
+1. You can earn LBC for helping with various tasks. Talk to us on [Discord Chat](https://chat.lbry.io/) if you're interested in additional testing or helping the community.
-   you're interested in additional testing or helping the community. 
 1. [Contributing](https://lbry.tech/contribute) to the project as a developer/engineer.
 1. Research and complete LBRY [bounties](https://lbry.io/bounty).
 1. Buy them: see [Exchanges](/faq/exchanges)
-1. Mine them: see [Mining](/faq/mining-credits). 
+1. Mine them: see [Mining](/faq/mining-credits).
 1. [Publish](https://lbry.io/faq/how-to-publish) content: when you publish your own content to the LBRY network, you can set an LBC price of your choice on it.
-

content/faq/earn-income.md

@@ -3,16 +3,17 @@ title: How does LBRY benefit content creators? Can I earn money using LBRY?
 category: publisher
 order: 2
 ---
-In our AMA title, we pitched LBRY as a “community-driven” YouTube alternative that could “save the internet.” That’s a lot of big talk, but what does it mean for the people who care most about the changes happening on YouTube – the content creators?
 
-If you are earning money from your videos on YouTube right now, you are likely familiar with the recent controversies over videos being “de-monetized” for containing content unfriendly to advertisers. It’s no surprise that YouTube caters to advertisers because ultimately, that's their main revenue stream.
+In our AMA title, we pitched LBRY as a "community-driven" YouTube alternative that could "save the internet." That's a lot of big talk, but what does it mean for the people who care most about the changes happening on YouTube – the content creators?
 
-LBRY is not an ad-driven media service. In fact, it’s not even a traditional media service at all. LBRY is an open protocol that allows you to publish your content to the network at no cost to you and allows you to set a price per stream or download if you wish. Because LBRY is a protocol and not a corporate store, there is no approval process for content to be listed and no authority that can “de-monetize” your videos. That’s between you and your audience.
+If you are earning money from your videos on YouTube right now, you are likely familiar with the recent controversies over videos being "de-monetized" for containing content unfriendly to advertisers. It's no surprise that YouTube caters to advertisers because ultimately, that's their main revenue stream.
 
-With LBRY, pricing is completely at the discretion of the creator, and 100% of that price goes to the creator. Compare this to iTunes’ fixed pricing tiers and 30% commission of every sale.
+LBRY is not an ad-driven media service. In fact, it's not even a traditional media service at all. LBRY is an open protocol that allows you to publish your content to the network at no cost to you and allows you to set a price per stream or download if you wish. Because LBRY is a protocol and not a corporate store, there is no approval process for content to be listed and no authority that can "de-monetize" your videos. That's between you and your audience.
+
+With LBRY, pricing is completely at the discretion of the creator, and 100% of that price goes to the creator. Compare this to iTunes' fixed pricing tiers and 30% commission of every sale.
 
 Because LBRY uses digital currency (a la Bitcoin), creators can accept micropayments for every view without worrying about credit card processing fees. Or a studio could use LBRY to distribute a theatrical release to independent theaters and charge thousands of dollars per download. The only constraint on pricing is what your viewers are willing to pay.
 
-With YouTube monetization, creators earn a variable amount based on viewers’ engagement with ads. There is no set formula, but we’ve found a reasonable guesstimate of around [$2 per thousand views](https://www.quora.com/How-much-does-YouTube-pay-partners-for-their-content). This works out to a penny per 5 views. So on LBRY, if you charge just one penny per view (a price any viewer would pay without a second thought), you may get 5X the per-view earnings you’d get from YouTube instantly!
+With YouTube monetization, creators earn a variable amount based on viewers' engagement with ads. There is no set formula, but we've found a reasonable guesstimate of around [$2 per thousand views](https://www.quora.com/How-much-does-YouTube-pay-partners-for-their-content). This works out to a penny per 5 views. So on LBRY, if you charge just one penny per view (a price any viewer would pay without a second thought), you may get 5X the per-view earnings you'd get from YouTube instantly!
 
 Furthermore, you can share content of any type – video, music, ebooks, images, podcasts – all on the same platform.

content/faq/exchanges.md

@@ -9,15 +9,15 @@ We are listed on several exchanges. You can buy or sell LBRY Credits at one of t
 - [Bittrex](https://bittrex.com/Market/Index?MarketName=BTC-LBC)
 - [Poloniex](https://poloniex.com/exchange#btc_lbc)
 - [Upbit](https://upbit.com/exchange?code=CRIX.UPBIT.BTC-LBC)
-- [Instant Bitex](https://instantbitex.com/)
+- [Instant Bitex](https://instantbitex.com)
-- [BitSquare](https://bitsquare.io/)
+- [BitSquare](https://bitsquare.io)
 - [Coinspot](https://www.coinspot.com.au/buy/lbc)
 - [Trade by Trade](https://app.tradebytrade.com/exchange-one)
-- [Coin Delta](https://coindelta.com/)
+- [Coin Delta](https://coindelta.com)
 - [Coindeal](https://frontend.coindeal.com/market/trade.html?pair=LBC/BTC)
 
 ### Instant Exchanges
 - [Shapeshift](https://shapeshift.io) (Requires free membership account now)
 - [Changelly](https://changelly.com/exchange/BTC/LBC/1)
 - [ChangeNow](https://changenow.io/exchange?amount=1&from=btc&to=lbc)
-- [Simple Swap](https://simpleswap.io/)
+- [Simple Swap](https://simpleswap.io)

content/faq/host-content.md

@@ -5,11 +5,10 @@ category: getstarted
 
 Right now, it's simple: you host what you download.
 
-While the LBRY app is running, it communicates to the network whatever
+While the LBRY app is running, it communicates to the network whatever content you're making available.
-content you're making available.
+
+Think of it like how torrents or any other peer-to-peer (P2P) service works. First, you download a file from the host(s) that have made it available via seeding.
 
-Think of it like how torrents or any other peer-to-peer (P2P) service 
-works. First, you download a file from the host(s) that have made it available via seeding. 
 When the download has finished, you become a host in the network (seeder) that other people can download from.
 
 **Please note: Hosting fees are currently disabled on the network as we're currently working on a better way to implement the fee structure.**

content/faq/how-to-backup-wallet.md

@@ -2,7 +2,8 @@
 title: How do I back up my LBRY wallet?
 category: wallet
 ---
-The LBRY application relies on blockchain technology and the LBRY Credits (LBC) cryptocurrency in order to participate in the network. These LBC are stored in a wallet (data file on your PC) which is generated with each LBRY installation (think of your credits as digital cash on your PC). A wallet contains your funds, channel data, and claims (any uploads). It is important to understand that the wallet is not stored on any LBRY servers and as such, users are responsible for its safeguarding and making sure a backup (copy of the wallet file) is available in the event that it is lost. If a wallet is lost or needs to be transferred, follow the [restore procedures below](#restore).     
+
+The LBRY application relies on blockchain technology and the LBRY Credits (LBC) cryptocurrency in order to participate in the network. These LBC are stored in a wallet (data file on your PC) which is generated with each LBRY installation (think of your credits as digital cash on your PC). A wallet contains your funds, channel data, and claims (any uploads). It is important to understand that the wallet is not stored on any LBRY servers and as such, users are responsible for its safeguarding and making sure a backup (copy of the wallet file) is available in the event that it is lost. If a wallet is lost or needs to be transferred, follow the [restore procedures below](#restore).
 
 *Note: Wallets should be re-backed up after creating new Channels/Identities (this is stored directly in the wallet file, and not part of the seed/restore process at the moment).*
 
@@ -32,22 +33,22 @@ The easiest way to find the location of your LBRY Android wallet is via the [And
 ![Find wallet](https://spee.ch/b3535b68750ad69c48566cb028c67d323d1fdeb9/walli.jpg)
 
 ## How do I backup my LBRY Android app wallet? {#android}
-The Android wallet will be removed if you uninstall the app or clear data. Scroll to the top of this page to learn more about your wallet. 
+The Android wallet will be removed if you uninstall the app or clear data. Scroll to the top of this page to learn more about your wallet.
 *Please note that this may vary with each Android device*
 1. Open your favorite file manager, navigate to `Internal storage/android/data/io.lbry.browser/files/lbryum/wallets`
 2. Copy the default_wallet to any other location on your device, i.e. your SD card or another directory on the Internal Storage
 
 ## Wallet migration with 0.30 SDK release {#migration}
 
-If you have run one of the latest Desktop or Android releases, you'll notice a file named `old_lbryum_wallet_1` in your wallets folder. This is a backup prior to the migration to the new wallet that's part of the 0.30 LBRY SDK release. This can be backed up for safekeeping or discarded if your current wallet is showing the right balance, claims and channels. 
+If you have run one of the latest Desktop or Android releases, you'll notice a file named `old_lbryum_wallet_1` in your wallets folder. This is a backup prior to the migration to the new wallet that's part of the 0.30 LBRY SDK release. This can be backed up for safekeeping or discarded if your current wallet is showing the right balance, claims and channels.
 
 ## How do I restore my wallet? {#restore}
 
-The process of restoring a previously backed up wallet is fairly simple. After installing LBRY, you would find the location of your wallet (see section above on finding the wallet) and replace the newly generated wallet with your backup copy (LBRY needs to be completely shut down when you do so). Before replacing the existing `default_wallet`, please confirm there are no credits inside of it by opening the LBRY app and checking the balance in the top right next to the bank icon - this should read 0 if the wallet is empty. Once the backed up `default_wallet` file is in place, start LBRY, and your balance should now be updated. 
+The process of restoring a previously backed up wallet is fairly simple. After installing LBRY, you would find the location of your wallet (see section above on finding the wallet) and replace the newly generated wallet with your backup copy (LBRY needs to be completely shut down when you do so). Before replacing the existing `default_wallet`, please confirm there are no credits inside of it by opening the LBRY app and checking the balance in the top right next to the bank icon - this should read 0 if the wallet is empty. Once the backed up `default_wallet` file is in place, start LBRY, and your balance should now be updated.
 
 ## Can I use the same wallet on mulitple PCs / installations?
 
-As of LBRY SDK 0.30 (December 2018), you can copy the default_wallet file to multiple installations and have them synced. You can even do so between PC + Android, as long as the wallet is not encrypted (Android does not support encryption yet). The only thing that won't sync at the moment is channels that are created after the file is copied (the file would need to be copied again to access the channels). 
+As of LBRY SDK 0.30 (December 2018), you can copy the default_wallet file to multiple installations and have them synced. You can even do so between PC + Android, as long as the wallet is not encrypted (Android does not support encryption yet). The only thing that won't sync at the moment is channels that are created after the file is copied (the file would need to be copied again to access the channels).
 
 ## I need help with backup or recovery, who can I reach out to?
 

content/faq/how-to-change-email.md

@@ -5,29 +5,29 @@ category: troubleshooting
 
 In certain cases, you may want to change the email connected to your LBRY App. LBRY stores the email address along with an access token which is unique to each user account. To clear this token, shutdown LBRY and see instructions below for each operating system.
 
-Clearing out this token will allow you to change your email or reset your private access token. When you start up LBRY after clearing the token, you can reconnect an email address by going to **Help** > **Set Email** in the About section.  After setting the email, your LBRY Rewards status should be transferred to the new account. If this does not happen, please reach out to us via [email](mailto:help@lbry.io) with your old/new email addresses. 
+Clearing out this token will allow you to change your email or reset your private access token. When you start up LBRY after clearing the token, you can reconnect an email address by going to **Help** > **Set Email** in the About section.  After setting the email, your LBRY Rewards status should be transferred to the new account. If this does not happen, please reach out to us via [email](mailto:help@lbry.io) with your old/new email addresses.
 
 ## Windows
 1. Open the Control Panel, find the Credentials Manager (may need change View By setting)
-1. Select **Windows Credentials**
+2. Select **Windows Credentials**
-1. Under Generic Credentials, select **LBRY/auth_token** and click **Remove**
+3. Under Generic Credentials, select **LBRY/auth_token** and click **Remove**
 
 ## MacOS
 1. Open the Mac Keychain (Click Finder > Go > Utilities > Keychain Access)
-1. Select the **Passwords** category on the left
+2. Select the **Passwords** category on the left
-1. Find **LBRY/auth_token** and remove it
+3. Find **LBRY/auth_token** and remove it
 
-## Ubuntu / Linux 
+## Ubuntu / Linux
-*(Exact steps may differ slightly)* 
+*(Exact steps may differ slightly)*
 1. Go to **Passwords and Keys**
-1. Select the **Login** folder
+2. Select the **Login** folder
-1. Find **LBRY/auth_token** and right click > Delete to remove it
+3. Find **LBRY/auth_token** and right click > Delete to remove it
 
 ## Android {#android}
 *(Exact steps may differ slightly)*
 *Before proceeding, please make sure to backup your wallet if there are funds in it*
 1. Go to phone settings
-1. Select Apps/Applications
+2. Select Apps/Applications
-1. Scroll down to find `LBRY Browser`
+3. Scroll down to find `LBRY Browser`
-1. Click on it and select storage. Click `Clear data`
+4. Click on it and select storage. Click `Clear data`
-1. Launch the LBRY app. It should ask for your new email
+5. Launch the LBRY app. It should ask for your new email

content/faq/how-to-change-port.md

@@ -8,13 +8,13 @@ If you see the error message `couldn't bind to port 3333`, it is likely that ano
 The most user friendly way to change the port permanently is to append the below line to the `daemon_settings.yml` in the `lbrynet` [directory](https://lbry.io/faq/lbry-directories). If it doesn't exist, create a new file named `daemon_settings.yml` and append:
 
     peer_port: 3334
-    
+
-Sample daemon_settings.yml (may vary by OS):   
+Sample daemon_settings.yml (may vary by OS):
 
     {download_directory: c:\users\lbry,
     peer_port: 3334}
 
-## Other Methods  
+## Other Methods
 To change the port once during runtime, set the LBRY_PEER_PORT env variable. Here's one way to do this:
 
     LBRY_PEER_PORT=3334 ./lbrynet-daemon

content/faq/how-to-clean-install-preserve.md

@@ -3,7 +3,7 @@ title: How do I perform a clean installation of LBRY while preserving important
 category: troubleshooting
 ---
 
-Under certain circumstances, particularly if you've tested earlier beta versions, it may be recommended that you perform a clean installation of LBRY.  This generally involves uninstalling the current LBRY application, removing various directories/files and then reinstalling the latest version of LBRY. Different operating systems use different folder locations, and [this post on directories](https://lbry.io/faq/lbry-directories) will help if you cannot locate the right files or folders.  
+Under certain circumstances, particularly if you've tested earlier beta versions, it may be recommended that you perform a clean installation of LBRY.  This generally involves uninstalling the current LBRY application, removing various directories/files and then reinstalling the latest version of LBRY. Different operating systems use different folder locations, and [this post on directories](https://lbry.io/faq/lbry-directories) will help if you cannot locate the right files or folders.
 
 After uninstalling LBRY, the working directories are left intact so that the application can be easily reinstalled without losing your application data and wallet file. Application data is in the lbrynet folder (LBRY folder for Mac), and it includes various database and configuration files. Wallet and blockchain data is in the lbryum folder. Typically, you will want to save your wallet and a handful of configuration/database files when performing a clean installation in order to keep your important data intact.
 
@@ -14,7 +14,7 @@ Note: after a clean install, you may be prompted again for your email. This is n
 2. Uninstall the LBRY application by accessing "Add or Remove Programs" via the Control Panel.
 3. Type `%appdata%` into an Explorer window to find the working directories.
 4. Delete the entire LBRY folder.
-5. If you are performing a clean installation, delete the "lbryum" and "lbrynet" folders also **(!!THIS WILL DELETE YOUR WALLET FILE AND DATA!!)** then skip to step 8. 
+5. If you are performing a clean installation, delete the "lbryum" and "lbrynet" folders also **(!!THIS WILL DELETE YOUR WALLET FILE AND DATA!!)** then skip to step 8.
 6. Navigate to the "lbryum" folder and delete the `blockchain_headers` file.
 7. Navigate to the "lbrynet" folder and delete all items while leaving the following:
  1. `blobfiles folder` - stores encrypted downloaded files which are used for hosting.
@@ -40,7 +40,7 @@ Note: after a clean install, you may be prompted again for your email. This is n
 9. Launch LBRY by starting it from the Applications folder.  You can add it to your dock for easier access.  If you kept your data and wallet file, your balance and content should be reflected.
 
 ## Ubuntu / Linux
-*(Exact steps may vary per distro)* 
+*(Exact steps may vary per distro)*
 1. Reboot your PC (this is to ensure that no LBRY processes are running).
 2. Uninstall the LBRY application by going to terminal and typing: sudo apt-get remove lbry. Y to confirm *(Ubuntu specific command)*.
 3. Open the File browser and navigate to the Home directory. Press Ctrl-H to view hidden files and folders.

content/faq/how-to-cli.md

@@ -3,25 +3,25 @@ title: How do I use the LBRY Command Line Interface (CLI) tool?
 category: powerusers
 ---
 
-As a power user, you may want to run your own commands against the LBRY SDK. This guide explains how to run any available commands from the [LBRY SDK documentation](https://lbry.tech/api/sdk). You must be running the LBRY app or daemon in order to interact with the protocol. 
+As a power user, you may want to run your own commands against the LBRY SDK. This guide explains how to run any available commands from the [LBRY SDK documentation](https://lbry.tech/api/sdk). You must be running the LBRY app or daemon in order to interact with the protocol.
 
 ## Windows
 1. Open a **Command Prompt** application window
-1. Type `cd "C:\Program Files\LBRY\resources\static\daemon"` ([32-bit located in Program Files(x86)]) and click Enter
+2. Type `cd "C:\Program Files\LBRY\resources\static\daemon"` ([32-bit located in Program Files(x86)]) and click Enter
-1. Type `lbrynet status` and click **Enter**. This will return the LBRYnet status data
+3. Type `lbrynet status` and click **Enter**. This will return the LBRYnet status data
-1. See examples below or [LBRY SDK documentation](https://lbry.tech/api/sdk) for additional commands
+4. See examples below or [LBRY SDK documentation](https://lbry.tech/api/sdk) for additional commands
 
 ## MacOS
 1. Open a **Terminal** window
-1. Type `cd /Applications/LBRY.app/Contents/Resources/static/daemon`
+2. Type `cd /Applications/LBRY.app/Contents/Resources/static/daemon`
-1. Type `./lbrynet status`  and click **Enter**. This will return the LBRYnet status data
+3. Type `./lbrynet status`  and click **Enter**. This will return the LBRYnet status data
-1. See examples below or [LBRY SDK documentation](https://lbry.tech/api/sdk) for additional commands
+4. See examples below or [LBRY SDK documentation](https://lbry.tech/api/sdk) for additional commands
 
-## Ubuntu / Linux 
+## Ubuntu / Linux
 1. Open a **Terminal** window
-1. Type `cd /opt/LBRY/resources/static/daemon`
+2. Type `cd /opt/LBRY/resources/static/daemon`
-1. Type `./lbrynet status`  and click **Enter**. This will return the LBRYnet status data
+3. Type `./lbrynet status`  and click **Enter**. This will return the LBRYnet status data
-1. See examples below or [LBRY SDK documentation](https://lbry.tech/api/sdk) for additional commands
+4. See examples below or [LBRY SDK documentation](https://lbry.tech/api/sdk) for additional commands
 
 ## Common/Sample Commands
 - `lbrynet claim_list_mine` - Show list of own claims, including channels

content/faq/how-to-find-lbry-log-file.md

@@ -5,33 +5,32 @@ category: troubleshooting
 
 In certain cases, we may ask you to send us your log file(s).  The current log file is titled `lbrynet.log` (or just `lbrynet` if you have file extensions hidden) and is archived each time the files reaches 2MB. Older log files are copied to `lbrynet.log.<#>`. Typically only the lbrynet.log file is required, but we may ask for the others depending on the situation.  Since each Operating System has its own set of working directories, use the below guide in order to locate the log file(s).
 
- **lbrynet.log files may contain your IP address. While sharing this is not inherently dangerous, if you desire maximum privacy, please mask it before posting to public websites.**
+**lbrynet.log files may contain your IP address. While sharing this is not inherently dangerous, if you desire maximum privacy, please mask it before posting to public websites.**
- 
+
- ### Find Logs via the LBRY App
+### Find Logs via the LBRY App
- You are able to open the log folder from the Help tab in the LBRY app.
+You are able to open the log folder from the Help tab in the LBRY app.
- From the LBRY App, click on Help. Next, click on "Open Log Folder"
+From the LBRY App, click on Help. Next, click on "Open Log Folder"
- ![log](https://spee.ch/a/helps.jpeg)
+![log](https://spee.ch/a/helps.jpeg)
- The folder will be highlighted, so just double click to open and here you will see "lbrynet.log".
+The folder will be highlighted, so just double click to open and here you will see "lbrynet.log".
- 
 
 ### Find Logs Manually
 ## Windows
 1. Open File Explorer (Keyboard shortcut: Windows Key + E).
-1. Type `%localappdata%\lbry\lbrynet` (or `%appdata%\lbrynet` if you originally installed v0.14 or earlier) into the address bar and click Enter.
+2. Type `%localappdata%\lbry\lbrynet` (or `%appdata%\lbrynet` if you originally installed v0.14 or earlier) into the address bar and click Enter.
-2. Here you will see the `lbrynet.log` file and any archives. 
+3. Here you will see the `lbrynet.log` file and any archives.
 
 ## MacOS
 1. Open Finder.
-1. Click Go in the top menu and choose "Go To Folder".
+2. Click Go in the top menu and choose "Go To Folder".
-1. Type "~/Library/Application Support/LBRY" and then click go.
+3. Type "~/Library/Application Support/LBRY" and then click go.
-2. Here you will see the `lbrynet.log` file and any archives. 
+4. Here you will see the `lbrynet.log` file and any archives.
 
-## Ubuntu / Linux *(Exact steps may differ slightly)* 
+## Ubuntu / Linux *(Exact steps may differ slightly)*
 1. Navigate to your home directory. Ensure hidden files and folders are shown if using a graphical file explorer.
 2. Navigate to the `.local/share/lbry/lbrynet` folder (or `~/.lbrynet` if you originally installed v0.14 or earlier).
-3. Here you will see the `lbrynet.log` file and any archives. 
+3. Here you will see the `lbrynet.log` file and any archives.
 
-## Android *(Exact steps may differ slightly)* 
+## Android *(Exact steps may differ slightly)*
 1. Launch your favorite file explorer.
 2. Navigate to `Internal storage\android\data\io.lbry.browser->files\lbrynet`.
-3. Here you will see the `lbrynet.log` file and any archives. 
+3. Here you will see the `lbrynet.log` file and any archives.

content/faq/how-to-get-lbry-command-line.md

@@ -5,6 +5,6 @@ category: powerusers
 
 The LBRY project sources are hosted on [GitHub](https://github.com/lbryio).
 
-To install LBRY from source, you'll need the [lbry](https://github.com/lbryio/lbry) repository for the LBRY SDK and [lbry-desktop](https://github.com/lbryio/lbry-desktop) repository for the Desktop application. Further documentation is available in the respective repositories, READMEs and [contributing](https://lbry.tech/contribute) documentation. 
+To install LBRY from source, you'll need the [lbry](https://github.com/lbryio/lbry) repository for the LBRY SDK and [lbry-desktop](https://github.com/lbryio/lbry-desktop) repository for the Desktop application. Further documentation is available in the respective repositories, READMEs and [contributing](https://lbry.tech/contribute) documentation.
 
 You can find more information about building on and with LBRY at [https://lbry.tech](https://lbry.tech)

content/faq/how-to-publish.md

@@ -120,7 +120,7 @@ LBRY URLs can be shared with anyone, but they will require the LBRY app in order
 
 ### I'm an advanced user, is there more I can poke around with?
 
-Advanced users can check out the [API/CLI](https://lbryio.github.io/lbry/) documentation for command line / API options.
+Advanced users can check out the [API/CLI](https://lbryio.github.io/lbry) documentation for command line / API options.
 
 ### I'm confused and need some assistance, can you help?
 

content/faq/how-to-run-lbry.md

@@ -2,19 +2,20 @@
 title: How do I run LBRY from the command line?
 category: powerusers
 ---
-This guide will allow you to run the LBRY daemon which connects to the LBRY network. You can run the daemon separately in this fashion without having to start the LBRY app. If the LBRY app is started, it will utilize the running daemon. 
+
+This guide will allow you to run the LBRY daemon which connects to the LBRY network. You can run the daemon separately in this fashion without having to start the LBRY app. If the LBRY app is started, it will utilize the running daemon.
 
 ## Windows
 1. Open a **Command Prompt** application window
-1. Type `cd "C:\Program Files\LBRY\resources\static\daemon"` ([32-bit located in Program Files(x86)]) and click Enter
+2. Type `cd "C:\Program Files\LBRY\resources\static\daemon"` ([32-bit located in Program Files(x86)]) and click Enter
-1. Type `lbrynet start` and click Enter. 
+3. Type `lbrynet start` and click Enter
 
 ## MacOS
 1. Open a **Terminal** window
-1. Type `cd /Applications/LBRY.app/Contents/Resources/static/daemon`
+2. Type `cd /Applications/LBRY.app/Contents/Resources/static/daemon`
-1. Type `./lbrynet start` and click Enter. 
+3. Type `./lbrynet start` and click Enter
 
-## Ubuntu / Linux 
+## Ubuntu / Linux
 1. Open a **Terminal** window
-1. Type `cd /opt/LBRY/resources/static/daemon` or build location if running from source 
+2. Type `cd /opt/LBRY/resources/static/daemon` or build location if running from source
-1. Type `./lbrynet start` and click Enter. 
+3. Type `./lbrynet start` and click Enter

content/faq/incompatible-protocol-version.md

@@ -10,9 +10,9 @@ The most likely cause of this error is an old version was running during the ins
 
 ### How to Fix
 
-1. Click `Quit Daemon` in the LBRY app to kill the LBRY network process. 
+1. Click `Quit Daemon` in the LBRY app to kill the LBRY network process
-1. Restart your PC or ensure that any processes with "lbry" in the name are not running. 
+2. Restart your PC or ensure that any processes with "lbry" in the name are not running
-1. [Download](https://github.com/lbryio/lbry-desktop/releases) and re-install the latest version of LBRY. 
+3. [Download](https://github.com/lbryio/lbry-desktop/releases) and re-install the latest version of LBRY
-1. Start LBRY
+4. Start LBRY
 
-If you still receive this warning after completing the above steps, please [reach out to us](https://lbry.io/faq/how-to-report-bugs) for additional support. 
+If you still receive this warning after completing the above steps, please [reach out to us](https://lbry.io/faq/how-to-report-bugs) for additional support.

content/faq/is-lbry-open-source.md

@@ -3,6 +3,6 @@ title: Is LBRY open source?
 category: powerusers
 ---
 
-All of the code we have written for LBRY is open source, and MIT licensed - even this very website! You can access it on [GitHub](https://github.com/lbryio/).
+All of the code we have written for LBRY is open source, and MIT licensed - even this very website! You can access it on [GitHub](https://github.com/lbryio).
 
 Learn more about the technologies on [lbry.tech](https://lbry.tech).

content/faq/lbry-basics.md

@@ -4,18 +4,18 @@ category: getstarted
 order: 1
 ---
 
-The LBRY App allows you to view free and paid content, upload your digital media for free or at a set price, tip your favorite creators, send/receive LBRY Credits (LBC) and earn credits through LBRY Rewards. The app runs on top of the [LBRY protocol](https://lbry.io/faq/what-is-lbry) which is a peer to peer, decentralized file sharing and payment network secured by blockchain technology. 
+The LBRY App allows you to view free and paid content, upload your digital media for free or at a set price, tip your favorite creators, send/receive LBRY Credits (LBC) and earn credits through LBRY Rewards. The app runs on top of the [LBRY protocol](https://lbry.io/faq/what-is-lbry) which is a peer to peer, decentralized file sharing and payment network secured by blockchain technology.
 
 The purpose of this FAQ is to answer questions about some of the basic functionality available in the LBRY App. Please see our [other FAQ entries](https://lbry.io/faq) for additional information.
 
 ### What is the purpose of having my email connected to LBRY?
-Emails are collected to authenticate and [uniquely identify](https://lbry.io/faq/identity-requirements) users so that they can be eligible for [LBRY Rewards](#rewards), sync subscription data and to stay up to date on the latest LBRY happenings. No other data is stored with your email login. All other data, including your [wallet](#wallet), [downloads](#data) and published content are stored locally on your computer. You can find your connected email by going to Settings (gear icon in the top right) > Help > Connected email. 
+Emails are collected to authenticate and [uniquely identify](https://lbry.io/faq/identity-requirements) users so that they can be eligible for [LBRY Rewards](#rewards), sync subscription data and to stay up to date on the latest LBRY happenings. No other data is stored with your email login. All other data, including your [wallet](#wallet), [downloads](#data) and published content are stored locally on your computer. You can find your connected email by going to Settings (gear icon in the top right) > Help > Connected email.
 
 ### How do I change my LBRY connected email?
 If you ever need to change your LBRY email address or sign out, please see [this guide](https://lbry.io/faq/how-to-change-email). If you sign into a new email and need to transfer your verification status, you'll need to [reach out to us](mailto:help@lbryio) in order to link your accounts. Please do not verify again to obtain rewards on a 2nd account; your rewards account may be disabled for abuse.
 
 ### What if I want to run LBRY on multiple computers or different Windows accounts?
-If you want to run the LBRY app on multiple PCs or on other platforms like Android, you can sign in with the same email on all devices. Each installation will still have its own separate wallet file and download data (as mentioned above). Any rewards earned will be sent locally to the wallet where they are claimed. In the future, it is our goal to enable an opt-in wallet syncing service across all of your devices. 
+If you want to run the LBRY app on multiple PCs or on other platforms like Android, you can sign in with the same email on all devices. Each installation will still have it's own separate wallet file and download data (as mentioned above). Any rewards earned will be sent locally to the wallet where they are claimed. In the future, it is our goal to enable an opt-in wallet syncing service across all of your devices.
 
 ### What are LBRY Rewards? {#rewards}
 [LBRY Rewards](https://lbry.io/faq/rewards) are used to distribute LBRY Credits (LBC) to new and existing users by allowing them to explore app functions and complete tasks which generate LBC as a reward. In order to be eligible for rewards, you need to [verify your identity](https://lbry.io/faq/identity-requirements) which uniquely identifies you as an LBRY user.
@@ -25,54 +25,58 @@ A wallet is a secure, digital wallet used to store, send and receive cryptocurre
 
 To find your wallet in the LBRY App, click on `Wallet` on the left side of the App. Clicking it will bring you to the wallet overview page which shows your balance, available Rewards and recent transactions.
 
-The LBRY wallet is different from other cryptocurrencies because it also stores your shared content's metadata in the form of [claims](https://lbry.io/faq/naming) when using the [publishing features](https://lbry.io/faq/how-to-publish). Claim related [wallet transactions](https://lbry.io/faq/transaction-types) ensure that the blockchain uniquely identifies your content and the payment/tips can be routed appropriately. 
+The LBRY wallet is different from other cryptocurrencies because it also stores your shared content's metadata in the form of [claims](https://lbry.io/faq/naming) when using the [publishing features](https://lbry.io/faq/how-to-publish). Claim related [wallet transactions](https://lbry.io/faq/transaction-types) ensure that the blockchain uniquely identifies your content and the payment/tips can be routed appropriately.
 
 ### Where do I find my LBC wallet address?
 You can find your wallet address by first clicking on `Wallet` on the left side of the LBRY app.
+
 It'll come up with the wallet overview which shows your balance, LBC address and recent transactions.
+
 ![wallet](https://spee.ch/@clement:e/lbcwallet2.png)
-Your wallet holds multiple receiving addresses, and new ones can be generated by clicking "Get New Address". Your wallet balance is the sum total of all the LBC available in each of your addresses. 
+
+Your wallet holds multiple receiving addresses, and new ones can be generated by clicking "Get New Address". Your wallet balance is the sum total of all the LBC available in each of your addresses.
 
 ### Where can I get more LBRY Credits?
 The LBRY App is also integrated with [ShapeShift](https://lbry.io/faq/shapeshift) on the Get Credits tab of the wallet which allows you to convert cryptocurrencies into LBC or you can also [trade for LBC on exchanges](https://lbry.io/faq/exchanges).
 
 ### Where is all my LBRY App data stored? {#data}
-Please see the [LBRY directories FAQ page](https://lbry.io/faq/lbry-directories) for more information on where LBRY data is stored. Besides the internal LBRY data, you can also configure your LBRY download directory via the option at the top of the Settings page (gear icon in the top right). 
+Please see the [LBRY directories FAQ page](https://lbry.io/faq/lbry-directories) for more information on where LBRY data is stored. Besides the internal LBRY data, you can also configure your LBRY download directory via the option at the top of the Settings page (gear icon in the top right).
 
 ### Why is content downloaded to my PC even when I stream?
-LBRY is a decentralized peer to peer protocol, meaning there are no centralized servers or a single entity storing all the files (like YouTube). Instead, data is stored on each participant's computer locally (similar to BitTorrent). When you stream or download, LBRY will store the content in encrypted chunks called [blobs files](https://lbry.io/faq/lbry-directories) and seed it to the entire network so others can also download from you. It will also store the completed file in your downloads folder. Currently, there is no way to stop sharing or to store data temporarily, but you can always delete any files you don't want to seed from the LBRY app "Downloads" menu. 
+LBRY is a decentralized peer to peer protocol, meaning there are no centralized servers or a single entity storing all the files (like YouTube). Instead, data is stored on each participant's computer locally (similar to BitTorrent). When you stream or download, LBRY will store the content in encrypted chunks called [blobs files](https://lbry.io/faq/lbry-directories) and seed it to the entire network so others can also download from you. It will also store the completed file in your downloads folder. Currently, there is no way to stop sharing or to store data temporarily, but you can always delete any files you don't want to seed from the LBRY app "Downloads" menu.
 
 ### I want to share my content, where do I start? {#publish}
-Please refer to our [publishing guide](https://lbry.io/faq/how-to-publish) as a reference to assist you through the publishing process. 
+Please refer to our [publishing guide](https://lbry.io/faq/how-to-publish) as a reference to assist you through the publishing process.
 
 ### Where can I see my `1`Downloaded, `2`Published items and `3`History?
 They can all be found on the leftside of the LBRY app. Click `1` for Downloads to view downloaded files, `2` Publishes tab to view your published content and `3` to view watch or access history
 ![published](https://spee.ch/@clement:e/download-publish-hostory.png)
 
 ### How do I know if I'm sharing content and helping the LBRY network properly?
-The easiest way to confirm that you are sharing correctly is to determine if the port used for seeding (3333) is open to the rest of the LBRY network. To do so, type 3333 into [this port checking tool](http://www.canyouseeme.org) and check the result. It if shows "open", you are all set. If it shows "closed", you may need to check your router settings for UPnP options (set to enable) or forward TCP port 3333 and UDP Port 4444 to your local computer running the LBRY app. Firewall and NAT settings may also affect the availability of these ports. 
+The easiest way to confirm that you are sharing correctly is to determine if the port used for seeding (3333) is open to the rest of the LBRY network. To do so, type 3333 into [this port checking tool](http://www.canyouseeme.org) and check the result. It if shows "open", you are all set. If it shows "closed", you may need to check your router settings for UPnP options (set to enable) or forward TCP port 3333 and UDP Port 4444 to your local computer running the LBRY app. Firewall and NAT settings may also affect the availability of these ports.
 
 ### How can I search for content on LBRY?
 Searching in LBRY is as easy as typing your search term(s) into the address bar at the top and waiting for the results to return.
 When you press enter, you will be given both the direct url and search results
 ![Search](https://spee.ch/@clement:e/search-on-lbry.png)
 
-Clicking the Enter key will skip the search function and go directly to the URL typed (if it's valid) - this is only helpful if you know the exact URL you are trying to view. We are still in the process of optimizing the search results; please bear with us if you are having trouble finding something! 
+Clicking the Enter key will skip the search function and go directly to the URL typed (if it's valid) - this is only helpful if you know the exact URL you are trying to view. We are still in the process of optimizing the search results; please bear with us if you are having trouble finding something!
 
 ### How can I subscribe to and view my favorite channels?
 Navigate to a channel, or click on your favorite video(s), (LBRY URLs with an @ symbol in the front) and click on subscribe right below the video and channel name.
+
 ![Subscriptions](https://spee.ch/@clement:e/subscribe-subscription.png)
+
 To manage your subscriptions, you can simply click on **Subscriptions** right under Explore to view all of your subscribed channels on one page.
 
-
 ### Content consistently fails to stream or download, what should I do?
-Please see our [streaming guide](https://lbry.io/faq/unable-to-stream) if you consistently cannot download or stream content on LBRY. If you are having intermittent issues with download failures, try closing the LBRY app completely (including ending the "lbrynet-daemon" process in task manager) and re-initiating the download. Some files on the network may just not be available for various reasons - we'll work on filtering these out in the future. 
+Please see our [streaming guide](https://lbry.io/faq/unable-to-stream) if you consistently cannot download or stream content on LBRY. If you are having intermittent issues with download failures, try closing the LBRY app completely (including ending the "lbrynet-daemon" process in task manager) and re-initiating the download. Some files on the network may just not be available for various reasons - we'll work on filtering these out in the future.
 
 ### Some files don't open in the LBRY app, what's going on?
-Currently, the LBRY in-app player supports MP4 videos, MP3s, Images, GIFs, HTML and text files. Even though it doesn't support other formats from within the app, the files can still be externally opened by clicking the **Open** button or navigating to the file by clicking the **Downloaded to** file path on the content page. 
+Currently, the LBRY in-app player supports MP4 videos, MP3s, Images, GIFs, HTML and text files. Even though it doesn't support other formats from within the app, the files can still be externally opened by clicking the **Open** button or navigating to the file by clicking the **Downloaded to** file path on the content page.
 
 ### How do I begin troubleshooting problems myself?
-Please see [this guide](https://lbry.io/faq/how-to-find-lbry-log-file) on how to find your LBRY log files. These may provide you additional information to troubleshoot issues or to provide to the [support team](https://lbry.io/faq/support). 
+Please see [this guide](https://lbry.io/faq/how-to-find-lbry-log-file) on how to find your LBRY log files. These may provide you additional information to troubleshoot issues or to provide to the [support team](https://lbry.io/faq/support).
 
 ### I need additional help with the LBRY app, where can find it? {#support}
 Please check our [other FAQ entries](https://lbry.io/faq) for more information. We are always here to help as well, feel free to [reach out to us](https://lbry.io/faq/support).

content/faq/lbry-name.md

@@ -1,17 +1,18 @@
 ---
-title: What’s with the name LBRY?
+title: What's with the name LBRY?
 category: LBRY 101
 order: 3
 ---
-The very first question of newcomers is often, “How do you pronounce it?” Answer: library.
 
-“Is it an acronym?” No.
+The very first question of newcomers is often, "How do you pronounce it?" Answer: library.
 
-“Then why confuse people with the all-caps and no vowels?”
+"Is it an acronym?" No.
 
-First and foremost, LBRY is an internet protocol, just like HTTP. Content on LBRY is served to users via “LBRY names,” which look like this: lbry://itsawonderfullife. Very similar to the URL you type into your internet browser. LBRY is not just our branded name, but the character string we’ve chosen to lead our URIs (Uniform Resource Identifier).
+"Then why confuse people with the all-caps and no vowels?"
 
-It also serves as a truncated form of “library,” which reflects our mission: every film, song, book, and app ever made – available anywhere. Our vision for LBRY is to create a massive media repository for the 21st century that is built on a decentralized network controlled by its users. LBRY is to a traditional library what Amazon is to a department store.
+First and foremost, LBRY is an internet protocol, just like HTTP. Content on LBRY is served to users via "LBRY names," which look like this: lbry://itsawonderfullife. Very similar to the URL you type into your internet browser. LBRY is not just our branded name, but the character string we've chosen to lead our URIs (Uniform Resource Identifier).
+
+It also serves as a truncated form of "library," which reflects our mission: every film, song, book, and app ever made – available anywhere. Our vision for LBRY is to create a massive media repository for the 21st century that is built on a decentralized network controlled by its users. LBRY is to a traditional library what Amazon is to a department store.
 
 Is it an odd name? Perhaps. But we would kindly point to the success of brands like Hulu, Yahoo!, Etsy, Skype, Tumblr, and Zillow. In the end, a good company with a strong user base will be remembered regardless of its name. And a company with a brand as straightforward as Pets.com can still fail.
 

content/faq/lbry-revenue.md

@@ -2,12 +2,13 @@
 title: How does the company behind LBRY make money?
 category: other
 ---
-The LBRY protocol has a built-in digital currency that allows it to function called LBRY credits (LBC). These credits are very similar to bitcoins. Having a built-in digital currency creates an opportunity for a new kind of business that has never existed: [the protocol-first enterprise](https://medium.com/the-coinbase-blog/app-coins-and-the-dawn-of-the-decentralized-business-model-8b8c951e734f#.6mr8znoiu). LBRY Inc. has reserved 10% of all LBRY credits to fund continued development and provide profit for the founders. Since credits only gain value as the use of the protocol grows, the company has an incentive to continue developing this open-source project, and we can do it all without taking a percentage of anyone’s transactions.
 
-Here’s how LBRY Inc. **doesn’t** make money:
+The LBRY protocol has a built-in digital currency that allows it to function called LBRY credits (LBC). These credits are very similar to bitcoins. Having a built-in digital currency creates an opportunity for a new kind of business that has never existed: [the protocol-first enterprise](https://medium.com/the-coinbase-blog/app-coins-and-the-dawn-of-the-decentralized-business-model-8b8c951e734f#.6mr8znoiu). LBRY Inc. has reserved 10% of all LBRY credits to fund continued development and provide profit for the founders. Since credits only gain value as the use of the protocol grows, the company has an incentive to continue developing this open-source project, and we can do it all without taking a percentage of anyone's transactions.
 
-- **We do not take a cut of any transactions.** When users purchase content on LBRY, 100% of the listed price goes to the publisher. There is also a fee paid to the decentralized network of hosts that store and deliver the content to you. LBRY Inc. doesn’t take any of that unless the company is publishing or hosting content itself. The same rules apply to everyone.
+Here's how LBRY Inc. **doesn't** make money:
+
+- **We do not take a cut of any transactions.** When users purchase content on LBRY, 100% of the listed price goes to the publisher. There is also a fee paid to the decentralized network of hosts that store and deliver the content to you. LBRY Inc. doesn't take any of that unless the company is publishing or hosting content itself. The same rules apply to everyone.
 - **We do not earn profits from auctioning of names**, nor do we benefit from bidding wars over names. Our goal with the naming system is simply to allocate names most efficiently to benefit users.
-- **This is not a “pump and dump” scheme or vaporware.** See my essay [$1.2B Valuation and We Don’t Care](https://lbry.io/news/1.2b-market-cap-we-dont-care). LBRY credits have already experienced a bubble, and we paid it no mind. LBRY is real software with a live blockchain and thousands of active users. Our goal is to increase the long-term value of the protocol, which if adopted globally, will make our reserve many times more valuable than any short-term bubble. We’ve already invested 10,000 working hours into this project, and it will take many more, but we’re patient and focused on the future.
+- **This is not a "pump and dump" scheme or vaporware.** See my essay [$1.2B Valuation and We Don't Care](https://lbry.io/news/1.2b-market-cap-we-dont-care). LBRY credits have already experienced a bubble, and we paid it no mind. LBRY is real software with a live blockchain and thousands of active users. Our goal is to increase the long-term value of the protocol, which if adopted globally, will make our reserve many times more valuable than any short-term bubble. We've already invested 10,000 working hours into this project, and it will take many more, but we're patient and focused on the future.
 
-We are also exploring ways to generate revenue above our credit reserve, including providing value-added services to LBRY users and/or consulting to large content producers who want to harness the power of LBRY. But remember, by design, **we are not able** to single-handedly change the rules on users in an attempt to “monetize” all of your contributions to the network.
+We are also exploring ways to generate revenue above our credit reserve, including providing value-added services to LBRY users and/or consulting to large content producers who want to harness the power of LBRY. But remember, by design, **we are not able** to single-handedly change the rules on users in an attempt to "monetize" all of your contributions to the network.

content/faq/learn-more-tech.md

@@ -3,4 +3,5 @@ title: Where can I learn more about the technology behind LBRY?
 category: LBRY 101
 order: 5
 ---
-[lbry.tech](https://lbry.tech) is home to technical information about LBRY, an interactive playground to learn more about how it functions, resources on how to contribute and build on top of it, and much more. 
+
+[lbry.tech](https://lbry.tech) is home to technical information about LBRY, an interactive playground to learn more about how it functions, resources on how to contribute and build on top of it, and much more.

content/faq/mining-credits.md

@@ -2,6 +2,7 @@
 title: How do I mine LBRY credits?
 category: mining
 ---
+
 Library Credits (LBC) are mined over a 20-year Proof of Work period.
 Block rewards increase every 100 blocks by 1LBC, peak at 500, and decline slowly.
 

content/faq/mining-pools.md

@@ -16,7 +16,7 @@ The current breakdown of mining hash rates can be found on [Mining Pool Stats](h
 - [Zerg Pool](https://zergpool.com/)
 
 ## Established Pools
-- [LBRY Community Pool](http://lbrypool.com) <- Support the LBRY community with this pool!  
+- [LBRY Community Pool](http://lbrypool.com) <- Support the LBRY community with this pool!
 - [Luxor](https://mining.luxor.tech/lbry) <- Support the LBRY community with this pool!
 - [SuprNova](https://lbry.suprnova.cc/index.php?page=gettingstarted)
 - [CoinMine](https://www2.coinmine.pl/lbc/index.php?page=gettingstarted)

content/faq/naming.md

@@ -1,5 +1,5 @@
 ---
-title: How does LBRY naming work? Why don’t you just assign names the same way as internet domains?
+title: How does LBRY naming work? Why don't you just assign names the same way as internet domains?
 category: LBRY 101
 order: 4
 ---
@@ -21,7 +21,7 @@ We wanted a system that:
 - Allows multiple pieces of content to be located at a single keyword while keeping URLs as short and memorable as possible.
 - Prevents squatters from extorting creators.
 
-After meaningful consultation with creators, consumers, economists, computer scientists, and more, we devised LBRY’s naming system.
+After meaningful consultation with creators, consumers, economists, computer scientists, and more, we devised LBRY's naming system.
 
 ### How LBRY Does Naming
 
@@ -46,9 +46,9 @@ LBRY supports several types of URL resolution:
 
 ### Takeaways
 
-1. **Names aren’t bought, only reserved – no credits are lost, only put on deposit.** If you win the auction for a name, your credits are held with that name until you decide to withdraw them (at any time you wish). You aren’t buying the name from anyone, and no one profits off of the transfer of names. It’s just a test of who is willing to deposit the most credits toward a name. The only downside is that you can’t spend the credits on content or withdraw them while they are in reserve.
+1. **Names aren't bought, only reserved – no credits are lost, only put on deposit.** If you win the auction for a name, your credits are held with that name until you decide to withdraw them (at any time you wish). You aren't buying the name from anyone, and no one profits off of the transfer of names. It's just a test of who is willing to deposit the most credits toward a name. The only downside is that you can't spend the credits on content or withdraw them while they are in reserve.
 
-2. **The longer a community name is held, the longer it sticks.** Community-controlled URLs don't change instantly if more credits are designated – especially if you’ve held it for awhile. For every month a name is controlled, 1 day is added to the waiting period, for a maximum of 7 days (after 7 months). 
+2. **The longer a community name is held, the longer it sticks.** Community-controlled URLs don't change instantly if more credits are designated – especially if you've held it for awhile. For every month a name is controlled, 1 day is added to the waiting period, for a maximum of 7 days (after 7 months).
 
 3. **Everyone has a say.** If you claim lbry://bestmovieever and your film lives up to the hype, user tips and purchases are a strong force keeping your content there. If the community feels a URL resolution is incorrect, they can band together to change it anytime. This is a powerful force keeping bad actors at bay that has already proved useful.
 
@@ -58,8 +58,8 @@ For more details on claims, please see https://lbry.io/faq/claimtrie-implementat
 
 ### Experimentation
 
-Whether you're in love with this design or not, you'd likely agree it's unlike anything we've seen before. 
+Whether you're in love with this design or not, you'd likely agree it's unlike anything we've seen before.
 
-The bottom line is that LBRY is dedicated to providing true content freedom. We want to provide the world's best method for creators and consumers to share and monetize digital content without intermediaries. We happen to think this is a superior method to the alternatives, but we're also not dogmatic about it. 
+The bottom line is that LBRY is dedicated to providing true content freedom. We want to provide the world's best method for creators and consumers to share and monetize digital content without intermediaries. We happen to think this is a superior method to the alternatives, but we're also not dogmatic about it.
 
-We’re trying to solve a very hard problem in a novel way, and we're committed to giving this system a chance. 100,000 pieces of content in, it has worked seamlessly. But if we ever saw this system harming rather than helping, we wouldn't hesitate to change it.
+We're trying to solve a very hard problem in a novel way, and we're committed to giving this system a chance. 100,000 pieces of content in, it has worked seamlessly. But if we ever saw this system harming rather than helping, we wouldn't hesitate to change it.

content/faq/phone.md

@@ -12,7 +12,7 @@ Unfortunately, when running a rewards program, people may abuse it.
 Phone number verification provides an alternative method for LBRY users to participate in the [rewards](https://lbry.io/faq/rewards) program.
 
 ### What if my phone number isn't working?
-Certain regions, prepaid services and VOIP numbers will be blocked from phone verifications in order to combat abuse. If you are having trouble with getting a phone number accepted, please see one of the [other verification methods](https://lbry.io/faq/identity-requirements). 
+Certain regions, prepaid services and VOIP numbers will be blocked from phone verifications in order to combat abuse. If you are having trouble with getting a phone number accepted, please see one of the [other verification methods](https://lbry.io/faq/identity-requirements).
 
 ### What if the LBRY app says my phone number already exists?
-This usually means that there is another LBRY account/email address that's already associated with that number. If you are changing email addresses and need to link your accounts or you believe this is an error, please [reach out to us](mailto:help@lbry.io).  
+This usually means that there is another LBRY account/email address that's already associated with that number. If you are changing email addresses and need to link your accounts or you believe this is an error, please [reach out to us](mailto:help@lbry.io).