diff --git a/StandardizedClinicalDataTables/PERSON.md b/StandardizedClinicalDataTables/PERSON.md
index 02b5c41..c64e772 100644
--- a/StandardizedClinicalDataTables/PERSON.md
+++ b/StandardizedClinicalDataTables/PERSON.md
@@ -34,9 +34,7 @@ No.|Convention Description
 | 6  | Only one death date per individual can be used. If a patient has clinical activity (e.g. prescriptions filled, labs performed, etc) more than 60+ days after death you may want to drop the death record as it may have been falsely reported. If multiple records of death exist on multiple days you may select the death that you deem most reliable (e.g. death at discharge) or select the latest death date.|
 | 7  | If multiple death records occur, the date and the person have to be the same, but the cause can be different. Can be reported by different sources as well.|
 | 8  | If PERSON.DEATH_DATETIME cannot be precisely determined from the data, the best approximation should be used.|
-| 9  | The DEATH_DATETIME in the PERSON table should not be used as the way to find all deaths
- • `select * from PERSON where death_datetime is not null` should not be the practice
- • Rather, deaths should be found through the OBSERVATION table and the PERSON table is only used to determine which death date should be used in analysis.   |
+| 9  | The DEATH_DATETIME in the PERSON table should not be used as the way to find all deaths • `select * from PERSON where death_datetime is not null` should not be the practice • Rather, deaths should be found through the OBSERVATION table and the PERSON table is only used to determine which death date should be used in analysis.   |
 | 10 | Valid Gender, Race and Ethnicity Concepts each belong to their own Domain.|
 | 11 | Ethnicity in the OMOP CDM follows the OMB Standards for Data on Race and Ethnicity: Only distinctions between Hispanics and Non-Hispanics are made. |
 | 12 | Additional information is stored through references to other tables, such as the home address (location_id) or the primary care provider.|