 # ## Getting and setting config settings
 #
 # ```coffee
-#  # When no value has been set, `::get` returns the setting's default value
-#  atom.config.get('my-package.myKey') # -> 'defaultValue'
-#
-#  atom.config.set('my-package.myKey', 'value')
-#  atom.config.get('my-package.myKey') # -> 'value'
+# # With no value set, `::get` returns the setting's default value
+# atom.config.get('my-package.myKey') # -> 'defaultValue'
+#
+# atom.config.set('my-package.myKey', 'value')
+# atom.config.get('my-package.myKey') # -> 'value'
 # ```
 #
 # You may want to watch for changes. Use {::observe} to catch changes to the setting.

# ### Value Coercion
#
# Config settings each have a type specified by way of a
# [schema](json-schema.org). Let's say we have an integer setting that only
# allows numbers greater than 0:
#
# ```coffee
#  # When no value has been set, `::get` returns the setting's default value
#  atom.config.get('my-package.anInt') # -> 12
#
#  # The string will be coerced to the integer 123
#  atom.config.set('my-package.anInt', '123')
#  atom.config.get('my-package.anInt') # -> 123
#
#  # The string will be coerced to an integer, but it must be greater than 0, so is set to 1
#  atom.config.set('my-package.anInt', '-20')
#  atom.config.get('my-package.anInt') # -> 1
# ```
#
# ## Defining config settings for your package
#
# You specify a schema under a `config` key
#
# ```coffeescript
# module.exports =
#   # Your config schema
#   config:

# #### title and description
#
# The settings view will use the `title` and `description` keys display your
# config setting in a readable way. By default the settings view humanizes your
# config key, so `someSetting` becomes `Some Setting`. In some cases, this is
# confusing for users, and a more descriptive title is useful.
#
# Descriptions will be displayed below the title in the settings view.
#
