diff --git a/.github/release_workflow.md b/.github/release_workflow.md
index 1af23fca25..7afa24a6d6 100644
--- a/.github/release_workflow.md
+++ b/.github/release_workflow.md
@@ -75,5 +75,5 @@ Some other essential things to check throughout the release process -
 - As the release workflow is initiated by the `release` event, it's important to note that the default `GITHUB_REF` used by `actions/checkout` during the checkout process will correspond to the tag created during the release process. Consequently, the workflows will consistently build PyBaMM based on the commit associated with this tag. Should new commits be introduced to the `vYY.MM` branch, such as those addressing build issues, it becomes necessary to manually update this tag to point to the most recent commit -
   ```
   git tag -f <tag_name> <commit_hash>
-  git push origin <tag_name>  # can only be carried out by the maintainers
+  git push -f <pybamm-team/PyBaMM_remote_name> <tag_name>  # can only be carried out by the maintainers
   ```
diff --git a/.github/workflows/publish_pypi.yml b/.github/workflows/publish_pypi.yml
index 25fbafc0af..7d01fe0bee 100644
--- a/.github/workflows/publish_pypi.yml
+++ b/.github/workflows/publish_pypi.yml
@@ -10,7 +10,7 @@ on:
     inputs:
       target:
         description: 'Deployment target. Can be "pypi" or "testpypi"'
-        default: "pypi"
+        default: "testpypi"
       debug_enabled:
         type: boolean
         description: 'Run the build with tmate debugging enabled (https://github.com/marketplace/actions/debugging-with-tmate)'