[nongnu] elpa/git-commit f0c6e06ebf 1/3: manual: Update FAQ about performance

[ELPA Syncer]

branch: elpa/git-commit
commit f0c6e06ebf23eae45abbf846867590559a678525
Author: Jonas Bernoulli <jonas@bernoul.li>
Commit: Jonas Bernoulli <jonas@bernoul.li>

    manual: Update FAQ about performance
---
 docs/magit.org  | 8 ++++----
 docs/magit.texi | 8 ++++----
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/magit.org b/docs/magit.org
index 6c2c7c5af1..4e8f5523fc 100644
--- a/docs/magit.org
+++ b/docs/magit.org
@@ -8867,10 +8867,10 @@ See [[*Performance]].
 
 *** I changed several thousand files at once and now Magit is unusable
 
-Magit is *currently* not expected to work under such conditions. It sure
-would be nice if it did, and v2.5 will hopefully be a big step into
-that direction.  But it might take until v3.1 to accomplish fully
-satisfactory performance, because that requires some heavy refactoring.
+Magit is currently not expected to work well under such conditions.
+It sure would be nice if it did.  Reaching satisfactory performance
+under such conditions will require some heavy refactoring.  This is no
+small task but I hope to eventually find the time to make it happen.
 
 But for now we recommend you use the command line to complete this one
 commit.  Also see [[*Performance]].
diff --git a/docs/magit.texi b/docs/magit.texi
index 0b2d0bbba2..94f8a20568 100644
--- a/docs/magit.texi
+++ b/docs/magit.texi
@@ -10850,10 +10850,10 @@ See @ref{Performance}.
 @node I changed several thousand files at once and now Magit is unusable
 @appendixsubsec I changed several thousand files at once and now Magit is 
unusable
 
-Magit is @strong{currently} not expected to work under such conditions. It sure
-would be nice if it did, and v2.5 will hopefully be a big step into
-that direction.  But it might take until v3.1 to accomplish fully
-satisfactory performance, because that requires some heavy refactoring.
+Magit is currently not expected to work well under such conditions.
+It sure would be nice if it did.  Reaching satisfactory performance
+under such conditions will require some heavy refactoring.  This is no
+small task but I hope to eventually find the time to make it happen.
 
 But for now we recommend you use the command line to complete this one
 commit.  Also see @ref{Performance}.