+2 -2

src/docs/contributor/bug_reports.diviner

reviewed

··· 58 58 59 59 To update Phabricator, use a script like this one: 60 60 61 61 - http://www.phabricator.com/rsrc/install/update_phabricator.sh 61 61 + http://www.phabricator.com/rsrc/install/update_phabricator.sh 62 62 63 63 This script will require some adjustments depending on how your setup is 64 64 configured, which webserver you are using, etc. ··· 176 176 StackOverflow, Quora, Facebook and Twitter), but the upstream Maniphest is 177 177 the authoritative bug tracker and the best place to file: 178 178 179 179 - https://secure.phabricator.com/maniphest/task/create/ 179 179 + https://secure.phabricator.com/maniphest/task/create/ 180 180 181 181 If you don't want to file there (or, for example, your bug relates to being 182 182 unable to log in or unable to file an issue in Maniphest) you can file on any

+1 -1

src/docs/contributor/feature_requests.diviner

reviewed

··· 167 167 expectations about it, and have a good description of the problem you're trying 168 168 to solve, you're ready to file a feature request: 169 169 170 170 - https://secure.phabricator.com/maniphest/task/create/ 170 170 + https://secure.phabricator.com/maniphest/task/create/ 171 171 172 172 You can file feature requests in places other than Maniphest (like GitHub), but 173 173 we can address them far more effectively if you file them in the upstream.

+1 -1

src/docs/contributor/using_oauthserver.diviner

reviewed

··· 101 101 Simply include a query param with the key of "access_token" and the value 102 102 as the earlier obtained access token. For example: 103 103 104 104 - https://phabricator.example.com/api/user.whoami?access_token=ykc7ly7vtibj334oga4fnfbuvnwz4ocp 104 104 + https://phabricator.example.com/api/user.whoami?access_token=ykc7ly7vtibj334oga4fnfbuvnwz4ocp 105 105 106 106 If the token has expired or is otherwise invalid, the client will receive 107 107 an error indicating as such. In these cases, the client should re-initiate

+2 -2

src/docs/user/installation_guide.diviner

reviewed

··· 152 152 **If that doesn't work**, grab the package from PECL directly and follow the 153 153 build instructions there: 154 154 155 155 - http://pecl.php.net/package/APC 155 155 + http://pecl.php.net/package/APC 156 156 157 157 Installing APC is optional but **strongly recommended**, especially on 158 158 production hosts. ··· 180 180 For more details, see @{article:Configuration Guide}. You can use a script 181 181 similar to this one to automate the process: 182 182 183 183 - http://www.phabricator.com/rsrc/install/update_phabricator.sh 183 183 + http://www.phabricator.com/rsrc/install/update_phabricator.sh 184 184 185 185 = Next Steps = 186 186

+1 -1

src/docs/user/userguide/arcanist_coverage.diviner

reviewed

··· 32 32 If you're contributing, libphutil, Arcanist and Phabricator support coverage if 33 33 you install Xdebug: 34 34 35 35 - http://xdebug.org/ 35 35 + http://xdebug.org/ 36 36 37 37 It should be sufficient to correctly install Xdebug; coverage information will 38 38 be automatically enabled.

+1 -1

src/docs/user/userguide/diffusion.diviner

reviewed

··· 67 67 lengths. See this post on the LKML for a historical explanation of Git's 68 68 occasional internal use of 7-character hashes: 69 69 70 70 - https://lkml.org/lkml/2010/10/28/287 70 70 + https://lkml.org/lkml/2010/10/28/287 71 71 72 72 Because 7-character hashes are likely to collide for even moderately large 73 73 repositories, Diffusion generally uses either a 16-character prefix (which makes

+1 -1

src/docs/user/userguide/external_editor.diviner

reviewed

··· 48 48 General instructions for configuring some other editors and environments can be 49 49 found here: 50 50 51 51 - http://wiki.nette.org/en/howto-editor-link 51 51 + http://wiki.nette.org/en/howto-editor-link