-driver or Makefile templates. You can also create these templates by adding
-specially-named files to the storage directory. Driver templates are named
-starting with the name of the language and ending with "Driver" with no other
-file extension. Similarly, Makefile templates are named starting with the
-name of the language and ending with "Makefile" with no other file extension.
-
-Drivers provide additional code to implement running the test cases.
-Currently, a default driver template is only provided for C++. Makefiles
-should have the commands needed to compile the solution source code and/or
-make a driver program that will perform the tests. Since there is only
-a driver template for C++, there is similarly only a default Makefile template
-provided for C++. If you want automatic building and testing for one of the
-other languages, you will need to create a driver and Makefile template for
-that language. Here are more keywords that may be useful for these types of
-templates:
+driver or Makefile templates, though any keyword can be used in any type of
+template. You can create other types of templates by adding specially-named
+files to the storage directory. Driver templates are named starting with the
+name of the language and ending with "Driver" with no file extension.
+Similarly, Makefile templates are named starting with the name of the language
+and ending with "Makefile" with no file extension.
+
+Drivers provide additional code that allows the test cases to be run against
+your solution. Currently, Makefile and driver templates are only provided for
+the C++ language. Makefiles should have the commands needed to compile the
+solution source code and/or make a driver program that will perform the tests.
+If you want automatic building and testing for one of the other languages, you
+will need to create a driver and Makefile template for that language. Here
+are more keywords that may be useful for these types of templates: