chore: code suggestions

rome · Dec 12, 2022 · b419c14 · b419c14
1 parent 45954c2
commit b419c14
Showing 1 changed file with 8 additions and 4 deletions.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -177,11 +177,15 @@ When creating a new pull request, it's preferable to use a conventional commit-f
 
 Please use the template provided.
 
-If you PR requires some update on the website (new features, breaking changes, etc.), a new follow-up
-PR should be created against the "release" PR. If you can't create a new PR, please let the team know,
-the template should help to give all the information to the team.
+If your PR requires some update on the website (new features, breaking changes, etc.), you should create a new PR once the previous PR is successfully merged.
 
-The team will prepare a new PR after each new release, just search for "release" among the opened pull requests.
+Go to the issues section and check the pinned issues.
+You will find a _**pinned issue**_ that starts with "Documentation and Focus". Inside, you will find the details of:
+- the name of the branch where to point the PR that updates the documentation;
+- the PR that we will merge when the release is ready;
+
+If you can't create a new PR, please let the team know.
+The template should help to give all the information to the team.
 
 Here are some other scripts that you might find useful.