Fix nav errors, add custom "For more help" block | PM Handbook

src/content/docs/pm-handbook/guide/agile-sprints-profusion-of-terms.mdx

@@ -1,6 +1,5 @@
 ---
 title: "Agile vs sprints (vs Jira vs GitHub): A profusion of terms"
-contentType: page
 template: basicDoc
 topics:
   - Project management handbook
@@ -18,7 +17,7 @@ Luckily, we don't need to define it from scratch. Wikipedia does [an admirable j
 
 For our team, that means our process is optimized to ship early and often. This lets us respond swiftly to changes in the product roadmap. More importantly, it ensures we validate our solutions with stakeholders, and that we're not letting valuable work sit around and get moldy when it could be out in the world making our users' lives better.
 
-## Sprint (AKA scrum) [#sprint]
+## Sprint (or scrum) [#sprint]
 
 This is the particular flavor of agile we follow. The sprint system (often referred to as scrum) is one major approach to Agile, along with other Agile systems such as Kanban. Sprint systems are often accompanied by a lot of jargon and best practices, but for our team the most essential elements are:
 
@@ -48,4 +47,8 @@ The primary function of squads is to simplify sprint planning, backlog grooming,
 
 Each squad is responsible for its own grooming and sprint planning, but the managers and scrum masters coordinate grooming to ensure we're meeting our overall goals as a team.
 
-![Lines of communication scale rapidly as you add people to a team. Where L is Lines and P is People, the formula is L=P((P/2)-0.5)](./images/lines_of_communication.png "Lines of communication versus the number of people on a team.")
+![Lines of communication scale rapidly as you add people to a team. Where L is Lines and P is People, the formula is L=P((P/2)-0.5)](./images/lines_of_communication.png "Lines of communication versus the number of people on a team.")
+
+## For more help
+
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).

src/content/docs/pm-handbook/guide/key-agile-principles.mdx

@@ -1,6 +1,5 @@
 ---
 title: "Key agile principles for our team"
-contentType: page
 template: basicDoc
 topics:
   - Project management handbook
@@ -47,4 +46,8 @@ Anyone can edit our open-sourced docs. With hundreds of Relics and users editing
 
 In order to reward teams that help us work this way, we prioritize this work in our queue. For work the writers need to do themselves, we ask for at least one full sprint of lead time. If someone comes to us the Tuesday after a sprint starts, that means they could be waiting up to two weeks for us to kick off work! But if someone edits the docs themselves, we promise to get their edit live within a 1 to 3 business day SLA.
 
-This lets us create win-wins: Rather than a simple "no," a requestor can decide whether they truly need that content out _now_ (in which case they can create that first draft) or whether they're okay waiting a week or two.
+This lets us create win-wins: Rather than a simple "no," a requestor can decide whether they truly need that content out _now_ (in which case they can create that first draft) or whether they're okay waiting a week or two.
+
+## For more help
+
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).

src/nav/pm-handbook.yml

@@ -6,6 +6,6 @@ pages:
     path: /docs/pm-handbook/guide/
     pages:
     - title: "Agile vs sprints: A profusion of terms"
-      path: /docs/pm-handbook/guide/agile-sprints-profusion-of-terms/
+      path: /docs/pm-handbook/guide/agile-sprints-profusion-of-terms
     - title: "Key agile principles"
-      path: /docs/pm-handbook/guide/key-agile-principles/
+      path: /docs/pm-handbook/guide/key-agile-principles