Fixes review comments

Author: gurkanindibay

.github/ISSUE_TEMPLATE/citus-enterprise-release-checklist-template.md

@@ -7,16 +7,10 @@ assignees: gurkanindibay
 
 ---
 
-## Several things to note here
-
-These instructions assume you have `$VERSION`, `$PROJECT`, and `$REPO` environment variables set in your shell (e.g. `10.0.2`, `citus`, and `citus`). With those set, code from most steps can be copy-pasted.
-
-**After this checklist, you're still not done: open a release checklist for Enterprise too!**
-
 # Update OS Packages
 ## Debian and RedHat
-- Change your directory to `packaging` repository directory & checkout `all-$PROJECT` branch.
-- [ ] Run the pipeline using branch name as all-$PROJECT https://github.com/citusdata/packaging/actions/workflows/update_package_properties.yml. Input tag name and if version is fancy, input the fancy version_no. Other parameters could be kept as is if you want
+- Change your directory to `packaging` repository directory & checkout `all-enterprise` branch.
+- [ ] Run the pipeline using branch name as all-enterprise https://github.com/citusdata/packaging/actions/workflows/update_package_properties.yml. Input tag name and if version is fancy, input the fancy version_no. Other parameters could be kept as is if you want
   - Then check the following (needed for both debian & redhat):
     - [ ] Updated `pkglatest` variable in the `pkgvars` file to `$VERSION.citus-1`
   - Then check the following (needed for debian):

.github/ISSUE_TEMPLATE/citus-packaging-request-template.md

@@ -7,16 +7,10 @@ assignees: gurkanindibay
 
 ---
 
-## Several things to note here
-
-These instructions assume you have `$VERSION`, `$PROJECT`, and `$REPO` environment variables set in your shell (e.g. `10.0.2`, `citus`, and `citus`). With those set, code from most steps can be copy-pasted.
-
-**After this checklist, you're still not done: open a release checklist for Enterprise too!**
-
 # Update OS Packages
 ## Debian and RedHat
-- Change your directory to `packaging` repository directory & checkout `all-$PROJECT` branch.
-- [ ] Run the pipeline using branch name as all-citus https://github.com/citusdata/packaging/actions/workflows/update_package_properties.yml. Input tag name and if version is fancy, input the fancy version_no. Other parameters could be kept as is if you want
+- Change your directory to `packaging` repository directory & checkout `all-citus` branch.
+- [ ] Run the pipeline using branch name as all-citus [update_package_properties workflow](https://github.com/citusdata/packaging/actions/workflows/update_package_properties.yml). Input tag name and if version is fancy, input the fancy version_no. Other parameters could be kept as is if you want
   - Then check the following (needed for both debian & redhat):
     - [ ] Updated `pkglatest` variable in the `pkgvars` file to `$VERSION.citus-1`
   - Then check the following (needed for debian):
@@ -55,7 +49,7 @@ Note that we create docker images for only the latest version of Citus. So, you
 
 # Update PGXN
 - [ ] Run https://github.com/citusdata/packaging/actions/workflows/update-pgxn-version.yml on packaging repo, and check the following:
-  - [ ] Check out the `pgxn-$PROJECT` branch of the [packaging repository](https://github.com/citusdata/packaging)
+  - [ ] Check out the `pgxn-citus branch of the [packaging repository](https://github.com/citusdata/packaging)
   - [ ] All version occurrences are bumped in `META.json`
   - [ ] All version occurrences are bumped in `pkgvars`
 - [ ] After merging, ensure the Github Actions build completed successfully (a new release should appear in PGXN eventually)

.github/ISSUE_TEMPLATE/pg-auto-failover-enterprise-release-checklist-template.md

@@ -7,16 +7,10 @@ assignees: gurkanindibay
 
 ---
 
-## Several things to note here
-
-These instructions assume you have `$VERSION`, `$PROJECT`, and `$REPO` environment variables set in your shell (e.g. `10.0.2`, `citus`, and `citus`). With those set, code from most steps can be copy-pasted.
-
-**After this checklist, you're still not done: open a release checklist for Enterprise too!**
-
 # Update OS Packages
 ## Debian and RedHat
-- Change your directory to `packaging` repository directory & checkout `all-$PROJECT` branch.
-- [ ] Run the pipeline using branch name as all-$PROJECT [update_package_properties workflow](https://github.com/citusdata/packaging/actions/workflows/update_package_properties.yml). Input tag name and if version is fancy, input the fancy version_no. Other parameters could be kept as is if you want
+- Change your directory to `packaging` repository directory & checkout `all-pgautofailover-enterprise` branch.
+- [ ] Run the pipeline using branch name as all-pgautofailover-enterprise [update_package_properties workflow](https://github.com/citusdata/packaging/actions/workflows/update_package_properties.yml). Input tag name and if version is fancy, input the fancy version_no. Other parameters could be kept as is if you want
   - Then check the following (needed for both debian & redhat):
     - [ ] Updated `pkglatest` variable in the `pkgvars` file to `$VERSION.citus-1`
   - Then check the following (needed for debian):

.github/ISSUE_TEMPLATE/pg-auto-failover-release-checklist-template.md

@@ -7,16 +7,10 @@ assignees: gurkanindibay
 
 ---
 
-## Several things to note here
-
-These instructions assume you have `$VERSION`, `$PROJECT`, and `$REPO` environment variables set in your shell (e.g. `10.0.2`, `citus`, and `citus`). With those set, code from most steps can be copy-pasted.
-
-**After this checklist, you're still not done: open a release checklist for Enterprise too!**
-
 # Update OS Packages
 ## Debian and RedHat
-- Change your directory to `packaging` repository directory & checkout `all-$PROJECT` branch.
-- [ ] Run the pipeline using branch name as all-project https://github.com/citusdata/packaging/actions/workflows/update_package_properties.yml. Input tag name and if version is fancy, input the fancy version_no. Other parameters could be kept as is if you want
+- Change your directory to `packaging` repository directory & checkout `all-pgautofailover` branch.
+- [ ] Run the pipeline using branch name as all-pgautofailover [update_package_properties workflow](https://github.com/citusdata/packaging/actions/workflows/update_package_properties.yml). Input tag name and if version is fancy, input the fancy version_no. Other parameters could be kept as is if you want
   - Then check the following (needed for both debian & redhat):
     - [ ] Updated `pkglatest` variable in the `pkgvars` file to `$VERSION.citus-1`
   - Then check the following (needed for debian):