Fix markdown-link-check errors.

contributing/pullrequest-submission-and-lifecycle.md

@@ -4,8 +4,6 @@
 - [Branch Prefixes](#branch-prefixes)
 - [Common Review Items](#common-review-items)
     - [Go Coding Style](#go-coding-style)
-    - [Resource Contribution Guidelines](#resource-contribution-guidelines)
-- [Changelog Process](#changelog-process)
 
 We appreciate direct contributions to the provider codebase. Here's what to
 expect:
@@ -29,16 +27,14 @@ expect:
 1. Once you believe your pull request is ready to be reviewed, ensure the
    pull request is not a draft pull request by [marking it ready for review](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)
    or removing `[WIP]` from the pull request title if necessary, and a
-   maintainer will review it. Follow [the checklists below](#checklists-for-contribution)
-   to help ensure that your contribution can be easily reviewed and potentially
-   merged.
+   maintainer will review it.
 
 1. One of Terraform's provider team members will look over your contribution and
    either approve it or provide comments letting you know if there is anything
    left to do. We'll try give you the opportunity to make the required changes yourself, but in some cases we may perform the changes ourselves if it makes sense to (minor changes, or for urgent issues).  We do our best to keep up with the volume of PRs waiting for
    review, but it may take some time depending on the complexity of the work.
 
-1. Once all outstanding comments and checklist items have been addressed, your
+1. Once all outstanding comments have been addressed, your
    contribution will be merged! Merged PRs will be included in the next
    Terraform release.