style(agile handbook): Fix formatting issue with list

src/content/docs/agile-handbook/sprint-mechanics/liaisonships.mdx

@@ -10,9 +10,9 @@ But those casual edits by themselves aren't enough to create a world-class produ
 
 To support that deeper expertise, we break our platform into a number of domain areas and assign each area a level of support:
 
-* **Active liaison**: A writer is actively developing docs in the area, either for a new feature release or for strategic improvements to the content.
-* **Point person**: A writer is on hand to provide expertise and content review, but we're not actively developing docs.
-* **Not actively supported**: We don't have a liaison or point person, but we'll provide help through the @hero process in #documentation.
+* **Active liaison**: A writer is actively developing docs in the area, either for a new feature release or for strategic improvements to the content.
+* **Point person**: A writer is on hand to provide expertise and content review, but we're not actively developing docs.
+* **Not actively supported**: We don't have a liaison or point person, but we'll provide help through the @hero process in #documentation.
 
 No matter what support level we assign to an area, the liaison is never the only person to edit! We all share ownership of the site, and you should expect that other writers will edit and contribute to your areas of expertise.
 
@@ -58,7 +58,9 @@ Not every project gets a liaisonship! For smaller projects, we'll encourage team
             Liaison
         </td>
         <td>
-            Work with your stakeholders as you define and refine your project plans. As the picture becomes clearer, create tickets in our backlog and schedule them into upcoming sprints. By the time your tickets reach a backlog grooming, you should have a clear sense of scope and resources. (For more on creating a great ticket, see [Ticket best practices](https://docs.newrelic.com/docs/agile-handbook/appendices/ticket-best-practices/).) You're likely to take assignment on many of the tickets for your project, but you may also collaborate with other writers and swarm to complete the work. 
+            Work with your stakeholders as you define and refine your project plans. As the picture becomes clearer, create tickets in our backlog and schedule them into upcoming sprints. By the time your tickets reach a backlog grooming, you should have a clear sense of scope and resources. (For more on creating a great ticket, see [Ticket best practices](https://docs.newrelic.com/docs/agile-handbook/appendices/ticket-best-practices/).) 
+
+            You're likely to take assignment on many of the tickets for your project, but you may also collaborate with other writers and swarm to complete the work. 
         </td>
     </tr>
     </tbody>