Improve PR description of the automatic PR (#213)

Author: wtrocki

.github/workflows/autoupdate-prod.yaml

@@ -53,23 +53,25 @@ jobs:
             2. Documentation style
             3. Transformation engine linting
 
+            > NOTE: New automation PRs need to be closed and reopened to trigger builds
+
             ## Important Details
 
-            1. If build is failing please check the logs and fix the issues in the OpenAPI file (openapi/atlas-api.yaml)
-            2. Do not attempt to manually fix any issues in the Golang Codebase as all changes are automatically generated. 
-            Fixes should be applied to the OpenAPI file (openapi/atlas-api.yaml) or ./tools engine in separate PR.
+            1. If the build is failing please check the logs and fix the issues in the OpenAPI file (openapi/atlas-api.yaml)
+            2. Do not attempt to manually fix any issues in the Golang code as all changes are automatically generated. 
+            Fixes should be applied to the OpenAPI file (openapi/atlas-api.yaml) or ./tools engine in a separate PR.
 
             ## Manual Review Procedure
 
             1. Review changes in the OpenAPI file (openapi/atlas-api.yaml)
-            2. If we see any breaking changes without new resource version (
-              - Review breaking changes listed in `Detect Breaking Changes` action
+            2. If we see any breaking changes [without a new resource version](https://github.com/mongodb/atlas-sdk-go/tree/main/tools/releaser#new-resource-version).
+              - View the log of breaking changes in the `Detect Breaking Changes` action
               - Checkout PR locally and run `make update-version`
-              - Provide breaking changes infomation in generated `./releaser/breaking_changes/{release_version}.md` file
+              - Provide breaking changes information in generated `./releaser/breaking_changes/{release_version}.md` file
               - Push your changes directly to the automation PR. 
-            3. If we have major version release request feedback from additional reviewer if possible.
-            4. Merge PR into main branch 
-            5. After merge automated release process will be triggered. 
+            3. If we have a major version release request feedback from additional reviewers if possible.
+            4. Merge PR into the main branch 
+            5. After the merge automated release process will be triggered.