Altering-the-Database.md

@@ -6,7 +6,7 @@ To start the code that interacts with the database is split into three parts:
 * A mock gateway
 * An RDS gateway
 
-All of which are in the GameServer/src/datasource package with the same prefix, ie `NPCQuestionRowDataGateway`, `NPCQuestionRowDataGatewayMock`, and `NPCQuestionRowDataGatewayRDS`
+All of which are in the GameServer/src/main/java/datasource package with the same prefix, ie `NPCQuestionRowDataGateway`, `NPCQuestionRowDataGatewayMock`, and `NPCQuestionRowDataGatewayRDS`
 
 The interface defines the methods that will be available to access the database. The Mock acts as the database in most tests. The RDS talks to the actual database hosted on Amazon's Web Services which is used when the game is being played and in the RDS tests.
 
@@ -18,7 +18,7 @@ There is one small caveat about running the tests however, you cannot run any sp
 
 #### Test data
 
-In addition to the tests there are also a couple of enums located in either GameServer/tests/testData/ (This one only contains data used by the area servers) or in GameShared/tests/testData/ (This one contains data used by both the area servers and the login server). These enums contain the test data for the tests and (when it's pushed, which is mentioned a little later) for the game when it's in testing mode (this is the default mode you use). In order to push these changes to the database you will have to use one of the programs in GameServer/tests/default package, GameShared/tests/default package, or LoginServer/tests/default package. These will drop the corresponding database tables, create the tables, and insert the data into them.
+In addition to the tests there are also a couple of enums located in either GameServer/src/main/java/datatypes (This one only contains data used by the area servers) or in GameShared/src/main/java/datatypes (This one contains data used by both the area servers and the login server). These enums contain the test data for the tests and (when it's pushed, which is mentioned a little later) for the game when it's in testing mode (this is the default mode you use). In order to push these changes to the database you will have to use one of the programs in GameServer/src/test/java/default package, GameShared/src/test/java/default package, or LoginServer/src/test/java/default package. These will drop the corresponding database tables, create the tables, and insert the data into them.
 
 ## The Mock Gateway
 
@@ -34,9 +34,9 @@ For the mock gateway file you need to make whatever change you need, this file i
 
 For the mock gateway test you need to make sure to update the finder test to make sure the data can be retrieved from the gateway and add or modify any other test methods you need for whatever is being modified in the mock (If you are only adding or removing a field you should only have to modify the finder method).
 
-#### Testdata
+#### Test Enums
 
-In some test methods you may notice we're using a couple of enums for the tests. If you're adding, removing, or modifying a field you will have to make that same change to every entry in the corresponding enum. For example if you're trying to add a field to the `NPCQuestionRowDataGatewayMock` you will have to add that field to every entry in the NPCQuestionsForTest file. All of these enums can be found in either GameServer/tests/testData/ or in GameShared/tests/testData/. Depending on the change it is usually a good idea to make one or more entries for the purposes of testing that functionality, this way you have a smaller chance of breaking existing tests.
+In some test methods you may notice we're using a couple of enums for the tests. If you're adding, removing, or modifying a field you will have to make that same change to every entry in the corresponding enum. For example if you're trying to add a field to the `NPCQuestionRowDataGatewayMock` you will have to add that field to every entry in the NPCQuestionsForTest file. All of these enums can be found in either GameServer/src/main/java/datatypes or in GameShared/src/main/java/datatypes. Depending on the change it is usually a good idea to make one or more entries for the purposes of testing that functionality, this way you have a smaller chance of breaking existing tests.
 
 ## The RDS Gateway