home.md

@@ -36,7 +36,7 @@ int main(){
     return 0;
 }
 ```
-A strict camel case would have this reader be named ``BufferedIntReader`` or ``IntBufferedReader``, but this has some shortcomings. First, by pushing the "variant" part of the naming to the end, we get good, automatic sorting of the classes. This helps in editors and in documentation that lexically similar implies logically similar.  Now, imagine what happens when we get around to templating the BufferedReader.  
+A strict camel case would have this reader be named ``BufferedIntReader`` or ``IntBufferedReader``, but this has some shortcomings. By pushing the "variant" part of the naming to the end with ``BufferedReader_Int`` and ``BufferedReader_Dbl``, we get good, automatic sorting of the classes. This helps in editors and in documentation: *lexically similar implies logically similar*.  Now, imagine what happens when we get around to templating the BufferedReader.  
 ```c++
 template <typename T>
 class BufferedReader {