Improve docs

README.md

@@ -7,7 +7,10 @@
 [![Used By](https://img.shields.io/sourcegraph/rrc/github.com/jimsmart/peanut.svg)](https://sourcegraph.com/github.com/jimsmart/peanut)
 [![Godoc](https://img.shields.io/badge/godoc-reference-blue.svg)](https://godoc.org/github.com/jimsmart/peanut)
 
-peanut writes data structs without ceremony in a variety of formats.
+peanut is a [Go](https://golang.org/) package to write tagged data structs in a variety of formats.
+
+Its primary purpose is to provide a single consistent interface
+for easy, ceremony-free persistence of record-based struct data.
 
 ## About
 
@@ -23,7 +26,7 @@ Get the package:
 go get github.com/jimsmart/peanut
 ```
 
-Use the package within your code (see examples below):
+Use the package within your code:
 
 ```go
 import "github.com/jimsmart/peanut"

TODO

@@ -2,30 +2,8 @@ TODO
 ====
 
 
-- Supported data types
- - string
- - bool
- - float64 
- - float32 
- - int
- - int8
- - int16
- - int32
- - int64
- - uint
- - uint8
- - uint16
- - uint32
- - uint64
-
-
-- Improve the examples in Godocs.
-
-
-
 - Writers
  - Should writers throw an error if the given type to write has no tagged fields?
- - Or should they simply fall back to using field names when tags are not present?
 
 
 - Logging for CSV and Excel writers on completion, detailing files written?
@@ -37,7 +15,6 @@ TODO
  - On second thoughts, it may simplify some of our code.
 
 
-
 New writer types
 ----------------
 

doc.go

@@ -1,6 +1,6 @@
-// Package peanut writes data structs in a variety of formats.
+// Package peanut writes tagged data structs in a variety of formats.
 // Its primary purpose is to provide a single consistent interface
-// for easy, ceremony-free persistence of struct data.
+// for easy, ceremony-free persistence of record-based struct data.
 //
 // Each distinct struct type sent to Write() is written to an individual file/table,
 // each named according to the name of the struct.