doc: minor changes in README files.

Change-Id: I5b21ade727f9c4bed6545e69d87082baafaefa2b
Reviewed-on: https://code.wireshark.org/review/26702
Reviewed-by: Anders Broman <a.broman58@gmail.com>

doc/README.design

@@ -52,7 +52,6 @@ routine that goes through all the packets in the capture; the loop does
 
 	}
 
-The "wtap_seek_read()" call read the packet data into memory; the
+The "wtap_seek_read()" call reads the packet data into memory; the
 "epan_dissect_new()" call "dissects" that data, building a tree
 structure for the fields in the packet.
-

doc/README.developer

@@ -1,5 +1,3 @@
-Tabsize: 4
-
 This file is a HOWTO for Wireshark developers. It describes general development
 and coding practices for contributing to Wireshark no matter which part of
 Wireshark you want to work on.

doc/README.dissector

@@ -1,5 +1,3 @@
-Tabsize: 4
-
 This file is a HOWTO for Wireshark developers interested in writing or working
 on Wireshark protocol dissectors. It describes expected code patterns and the
 use of some of the important functions and variables.

doc/README.stats_tree

@@ -111,7 +111,7 @@ the stats_tree API
  every stats_tree callback has a stats_tree* parameter (st), stats_tree is an obscure
  data structure which should be passed to the api functions.
 
-stats_tree_register( tapname, abbr, name, flags, packet_cb, init_cb, cleanup_cb);
+stats_tree_register(tapname, abbr, name, flags, packet_cb, init_cb, cleanup_cb);
  registers a new stats tree
 
 stats_tree_register_plugin(tapname, abbr, name, flags, packet_cb, init_cb, cleanup_cb);
@@ -210,6 +210,6 @@ stat_node_clear_flags functions. Currently these flags are defined:
 			bottom half. Each half is sorted normally. Top always appear
 			first :)
 
-You can find more examples of these in $srcdir/plugins/stats_tree/pinfo_stats_tree.c
+You can find more examples of these in $srcdir/plugins/epan/stats_tree/pinfo_stats_tree.c
 
 Luis E. G. Ontanon.