summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorpsychocrypt <psychocrypt@users.noreply.github.com>2017-08-02 20:38:57 +0200
committerGitHub <noreply@github.com>2017-08-02 20:38:57 +0200
commitb8cded7760ca7cbd466787980713c357c51b66a9 (patch)
treec6ef6871ce2c7f4f5a66dd335afa3d7a42b607cb
parentb64d5851aa857e035c573f4c6ecd7d9ab3cc3d48 (diff)
parentf2c8f0cc0c7a9663fd5bdfdbbbb7e5ae6c03df5c (diff)
downloadxmr-stak-b8cded7760ca7cbd466787980713c357c51b66a9.zip
xmr-stak-b8cded7760ca7cbd466787980713c357c51b66a9.tar.gz
Merge pull request #260 from notunderground/dev
fix typos in config.txt
-rw-r--r--config.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/config.txt b/config.txt
index 52d545b..36d10d4 100644
--- a/config.txt
+++ b/config.txt
@@ -27,8 +27,8 @@ null,
/*
* LARGE PAGE SUPPORT
- * Large pages need a properly set up OS. It can be difficult if you are not used to systems administation,
- * but the performace results are worth the trouble - you will get around 20% boost. Slow memory mode is
+ * Large pages need a properly set up OS. It can be difficult if you are not used to systems administration,
+ * but the performance results are worth the trouble - you will get around 20% boost. Slow memory mode is
* meant as a backup, you won't get stellar results there. If you are running into trouble, especially
* on Windows, please read the common issues in the README.
*
@@ -53,13 +53,13 @@ null,
* and "* hard memlock 262144". You can also do it Windows-style and simply run-as-root, but this is NOT
* recommended for security reasons.
*
- * Memory locking means that the kernel can't swap out the page to disk - something that is unlikey to happen on a
+ * Memory locking means that the kernel can't swap out the page to disk - something that is unlikely to happen on a
* command line system that isn't starved of memory. I haven't observed any difference on a CLI Linux system between
* locked and unlocked memory. If that is your setup see option "no_mlck".
*/
/*
- * use_slow_memory defines our behaviour with regards to large pages. There are three possible options here:
+ * use_slow_memory defines our behavior with regards to large pages. There are three possible options here:
* always - Don't even try to use large pages. Always use slow memory.
* warn - We will try to use large pages, but fall back to slow memory if that fails.
* no_mlck - This option is only relevant on Linux, where we can use large pages without locking memory.
@@ -70,7 +70,7 @@ null,
/*
* NiceHash mode
- * nicehash_nonce - Limit the noce to 3 bytes as required by nicehash. This cuts all the safety margins, and
+ * nicehash_nonce - Limit the nonce to 3 bytes as required by nicehash. This cuts all the safety margins, and
* if a block isn't found within 30 minutes then you might run into nonce collisions. Number
* of threads in this mode is hard-limited to 32.
*/
OpenPOWER on IntegriCloud