Fix accidental .address changes

Author: GeNiaaz

docs/DevOps.md

@@ -81,7 +81,7 @@ do the rest.
 Here are the steps to create a new release.
 
 1. Update the version number in 
-[`MainApp.java`](https://github.com/se-edu/addressbook-level3/tree/master/src/main/java/seedu/projectDescription/MainApp.java).
+[`MainApp.java`](https://github.com/se-edu/addressbook-level3/tree/master/src/main/java/seedu/address/MainApp.java).
 1. Generate a fat JAR file using Gradle (i.e., `gradlew shadow`).
 1. Tag the repo with the version number. e.g. `v0.1`
 1. [Create a new release using GitHub](https://help.github.com/articles/creating-releases/). Upload the JAR 

docs/DeveloperGuide.md

@@ -27,7 +27,9 @@ The ***Architecture Diagram*** given above explains the high-level design of the
 
 </div>
 
-**`Main`** has two classes called [`Main`](https://github.com/se-edu/addressbook-level3/tree/master/src/main/java/seedu/projectDescription/Main.java) and [`MainApp`](https://github.com/se-edu/addressbook-level3/tree/master/src/main/java/seedu/projectDescription/MainApp.java). It is responsible for,
+**`Main`** has two classes called [`Main`](https://github.com/se-edu/addressbook-level3/tree/master/src/main/java
+/seedu/address/Main.java) and [`MainApp`](https://github.com/se-edu/addressbook-level3/tree/master/src/main/java/seedu
+/address/MainApp.java). It is responsible for,
 * At app launch: Initializes the components in the correct sequence, and connects them up with each other.
 * At shut down: Shuts down the components and invokes cleanup methods where necessary.
 

docs/SettingUp.md

@@ -23,7 +23,7 @@ If you plan to use Intellij IDEA (highly recommended):
 1. **Import the project as a Gradle project**: Follow the guide [_[se-edu/guides] IDEA: Importing a Gradle project_](https://se-education.org/guides/tutorials/intellijImportGradleProject.html) to import the project into IDEA.<br>
   :exclamation: Note: Importing a Gradle project is slightly different from importing a normal Java project.
 1. **Verify the setup**:
-   1. Run the `seedu.projectDescription.Main` and try a few commands.
+   1. Run the `seedu.address.Main` and try a few commands.
    1. [Run the tests](Testing.md) to ensure they all pass.
 
 --------------------------------------------------------------------------------------------------------------------

docs/Testing.md

@@ -29,8 +29,8 @@ There are two ways to run tests.
 This project has three types of tests:
 
 1. *Unit tests* targeting the lowest level methods/classes.<br>
-   e.g. `seedu.projectDescription.commons.StringUtilTest`
+   e.g. `seedu.address.commons.StringUtilTest`
 1. *Integration tests* that are checking the integration of multiple code units (those code units are assumed to be working).<br>
-   e.g. `seedu.projectDescription.storage.StorageManagerTest`
+   e.g. `seedu.address.storage.StorageManagerTest`
 1. Hybrids of unit and integration tests. These test are checking multiple code units as well as how the are connected together.<br>
-   e.g. `seedu.projectDescription.logic.LogicManagerTest`
+   e.g. `seedu.address.logic.LogicManagerTest`

docs/tutorials/AddRemark.md

@@ -19,16 +19,16 @@ Looking in the `logic.command` package, you will notice that each existing comma
 the commands inherit from the abstract class `Command` which means that they must override `execute()`. Each `Command` returns an instance of `CommandResult` upon success and `CommandResult#feedbackToUser` is printed to the 
 `ResultDisplay`.
 
-Let’s start by creating a new `RemarkCommand` class in the `src/main/java/seedu/projectDescription/logic/command` directory.
+Let’s start by creating a new `RemarkCommand` class in the `src/main/java/seedu/address/logic/command` directory.
 
 For now, let’s keep `RemarkCommand` as simple as possible and print some output. We accomplish that by returning a `CommandResult` with an accompanying message.
 
 **`RemarkCommand.java`:**
 
 ``` java
-package seedu.projectDescription.logic.commands;
+package seedu.address.logic.commands;
 
-import seedu.projectDescription.model.Model;
+import seedu.address.model.Model;
 
 /**
  * Changes the remark of an existing project in the main catalogue.
@@ -93,7 +93,8 @@ We start by modifying the constructor of `RemarkCommand` to accept an `Index` an
 if our code is functioning as intended.
 
 ``` java
-import static seedu.projectDescription.commons.util.CollectionUtil.requireAllNonNull;
+import static seedu.address
+.commons.util.CollectionUtil.requireAllNonNull;
 //...
 public class RemarkCommand extends Command {
     //...
@@ -143,7 +144,9 @@ Your code should look something like [this](https://github.com/se-edu/addressboo
 
 Now let’s move on to writing a parser that will extract the index and remark from the input provided by the user.
 
-Create a `RemarkCommandParser` class in the `seedu.projectDescription.logic.parser` package. The class must extend the `Parser` interface.
+Create a `RemarkCommandParser` class in the `seedu.address
+.logic.parser` package. The class must extend the `Parser
+` interface.
 
 ![The relationship between Parser and RemarkCommandParser](../images/add-remark/ParserInterface.png)
 
@@ -235,7 +238,9 @@ Now that we have all the information that we need, let’s lay the groundwork fo
 
 ### Add a new `Remark` class
 
-Create a new `Remark` in `seedu.projectDescription.model.project`. Since a `Remark` is a field that is similar to `Address`, we can reuse a significant bit of code.
+Create a new `Remark` in `seedu.address
+.model.project`. Since a `Remark` is a field that is similar to `Address`, we can
+ reuse a significant bit of code.
 
 A copy-paste and search-replace later, you should have something like 
 [this](https://github.com/se-edu/addressbook-level3/commit/4516e099699baa9e2d51801bd26f016d812dedcc#diff-af2f075d24dfcd333876f0fbce321f25). Note how `Remark` has no 
@@ -251,7 +256,9 @@ These should be relatively simple changes.
 
 Without getting too deep into `fxml`, let’s go on a 5 minute adventure to get some placeholder text to show up for each project.
 
-Simply add the following to [`seedu.projectDescription.ui.ProjectCard`](https://github.com/se-edu/addressbook-level3/commit/850b78879582f38accb05dd20c245963c65ea599#diff-0c6b6abcfac8c205e075294f25e851fe).
+Simply add the following to [`seedu.address
+.ui.ProjectCard`](https://github.com/se-edu/addressbook-level3/commit
+/850b78879582f38accb05dd20c245963c65ea599#diff-0c6b6abcfac8c205e075294f25e851fe).
 
 **`ProjectCard.java`:**
 

docs/tutorials/TracingCode.md

@@ -32,7 +32,7 @@ Before we proceed, ensure that you have done the following:
 
 ## Setting a break point
 
-As you know, the first step of debugging is to put in a breakpoint where you want the debugger to pause the execution. For example, if you are trying to understand how the App starts up, you would put a breakpoint in the first statement of the `main` method. In our case, we would want to begin the tracing at the very point where the App start processing user input (i.e., somewhere in the UI component), and then trace through how the execution proceeds through the UI component. However, the execution path through a GUI is often somewhat obscure due to various *event-driven mechanisms* used by GUI frameworks, which happens to be the case here too. Therefore, let us put the breakpoint where the UI transfers control to the Logic component. According to the sequence diagram, the UI component yields control to the Logic component through a method named `execute`. Searching through the code base for `execute()` yields a promising candidate in `seedu.projectDescription.ui.CommandBox.CommandExecutor`.
+As you know, the first step of debugging is to put in a breakpoint where you want the debugger to pause the execution. For example, if you are trying to understand how the App starts up, you would put a breakpoint in the first statement of the `main` method. In our case, we would want to begin the tracing at the very point where the App start processing user input (i.e., somewhere in the UI component), and then trace through how the execution proceeds through the UI component. However, the execution path through a GUI is often somewhat obscure due to various *event-driven mechanisms* used by GUI frameworks, which happens to be the case here too. Therefore, let us put the breakpoint where the UI transfers control to the Logic component. According to the sequence diagram, the UI component yields control to the Logic component through a method named `execute`. Searching through the code base for `execute()` yields a promising candidate in `seedu.address.ui.CommandBox.CommandExecutor`.
 
 ![Using the `Search for target by projectName` feature. `Navigate` \> `Symbol`.](../images/tracing/Execute.png)
 

src/main/java/seedu/address/model/person/Address.java

@@ -20,7 +20,7 @@ public class Address {
     public final String value;
 
     /**
-     * Constructs an {@code ProjectDescription}.
+     * Constructs an {@code Address}.
      *
      * @param address A valid address
      */

src/main/java/seedu/address/model/person/Person.java

@@ -138,7 +138,7 @@ public String toString() {
                 .append(getPhone())
                 .append(" Email: ")
                 .append(getEmail())
-                .append(" ProjectDescription: ")
+                .append(" Address: ")
                 .append(getAddress())
                 .append(" Tags: ");
         getTags().forEach(builder::append);