diff --git a/Getting-Started/Getting-Started-Basic-Def.md b/Getting-Started/Getting-Started-Basic-Def.md
index 40787bd..c365645 100644
--- a/Getting-Started/Getting-Started-Basic-Def.md
+++ b/Getting-Started/Getting-Started-Basic-Def.md
@@ -157,7 +157,7 @@ later on.
 
 There are three flavors of key:
 
- - `SettingKey[T]`: a key with a value that never changes (the value is
+ - `SettingKey[T]`: a key with a value computed once (the value is
    computed one time when loading the project, and kept around).
  - `TaskKey[T]`: a key with a value that has to be recomputed each time,
    potentially creating side effects.
diff --git a/Getting-Started/Getting-Started-Custom-Settings.md b/Getting-Started/Getting-Started-Custom-Settings.md
index 35fbbcb..3e9c167 100644
--- a/Getting-Started/Getting-Started-Custom-Settings.md
+++ b/Getting-Started/Getting-Started-Custom-Settings.md
@@ -38,7 +38,7 @@ building."`).
 Remember from [[basic build definition|Getting Started Basic Def]] that the type parameter `T` in `SettingKey[T]`
 indicates the type of value a setting has. `T` in `TaskKey[T]` indicates the
 type of the task's result. Also remember from [[basic build definition|Getting Started Basic Def]]
-that a setting has a fixed value cached forever, while a task is re-computed
+that a setting has a fixed value until project reload, while a task is re-computed
 for every "task execution" (every time someone types a command at the sbt
 interactive prompt or in batch mode).