Improve pull_request_template and doccument

"inline documentation" conventions

.github/pull_request_template.md

@@ -1,14 +1,16 @@
-Resolves issue #
+Link issues resolved by this:
+Resolves #
 
 Changes/added features:
 -
-- 
+-
 
 The following short checklist should be used to make sure your PR is of good quality, and can be merged easily:
 - [ ] follows [project conventions](https://github.com/ContainerSolutions/terraform-examples#conventions)
 - [ ] follows [project principles](https://github.com/ContainerSolutions/terraform-examples#principles)
+- [ ] `./run.sh` works correctly for all new examples
 - [ ] CI checks pass
-- [ ] mergeable to main
+- [ ] mergeable to main (no conflicts)
 - [ ] resolved issues linked
 
 Reviewers:

README.md

@@ -76,6 +76,11 @@ The examples seek to be:
 - For help with automated testing
   - where possible, add some way to enable 'left-over' resources to be cleaned up, eg provider `default_tags` of `cs_terraform_examples` in AWS provider blocks
 
+- Add inline documentation for each Terraform code block
+  - `# Summary:` – 1-line summary of what this example does
+  - `# Documentation:` – add link to documentation before each block (terraform, provider, variable, resource, etc.)
+  - `# Explanation:` – add only where some extra explanation is needed
+
 ## GitHub Actions Workflow
 
 On every commit, the following tests run on all branches: