revi-archive/phorge-phorge
1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2024-12-18 19:40:55 +01:00
Code Issues Releases Wiki Activity

Fix two "proably" typos

Browse source 
Summary: Caught one of these while reviewing docs, grepped for the other one.

Test Plan: `grep`, reading

Reviewers: chad

Reviewed By: chad

Differential Revision: https://secure.phabricator.com/D16498
This commit is contained in:
epriestley 2016-09-06 08:47:20 -07:00
parent defee93851
commit 7eee5c5f6f
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
src/docs/user/field/performance.diviner
View file

@ -31,7 +31,7 @@ bug, not a configuration problem.
However, some pages are slow because Phabricator legitimately needs to do a lot However, some pages are slow because Phabricator legitimately needs to do a lot
of work to generate them. For example, if you write a 100MB wiki document, of work to generate them. For example, if you write a 100MB wiki document,
Phabricator will need substantial time to process it, it will take a long time Phabricator will need substantial time to process it, it will take a long time
to download over the network, and your browser will proably not be able to to download over the network, and your browser will probably not be able to
render it especially quickly. render it especially quickly.
We may be able to improve perfomance in some cases, but Phabricator is not We may be able to improve perfomance in some cases, but Phabricator is not

2
src/infrastructure/storage/lisk/PhabricatorLiskDAO.php
View file

@ -67,7 +67,7 @@ abstract class PhabricatorLiskDAO extends LiskDAO {
$connection = $this->newBasicConnection($database, $mode, $namespace); $connection = $this->newBasicConnection($database, $mode, $namespace);
} }
// TODO: This should be testing if the mode is "r", but that would proably // TODO: This should be testing if the mode is "r", but that would probably
// break a lot of things. Perform a more narrow test for readonly mode // break a lot of things. Perform a more narrow test for readonly mode
// until we have greater certainty that this works correctly most of the // until we have greater certainty that this works correctly most of the
// time. // time.