docs: releasing docs improvements

docs/releasing.md

@@ -10,7 +10,7 @@ geekdocFilePath: releasing.md
 
 ## Releasing ownCloud Web
 
-OwnCloud Web can be hosted standalone or as part of oCIS.
+OwnCloud Web can be hosted standalone for a dedicated oCIS backend or bundled as part of oCIS.
 
 ### Versioning
 
@@ -23,13 +23,7 @@ The highest type before a new release determines the version update number, so i
 1. Create a branch `release-$version` in <https://github.com/owncloud/web>.
 2. Create a folder in `changelog` for the release version and date `mkdir $major.$minor.$patchVersion_YYYY-MM-DD`.
 3. Move all changelog items from the `changelog/unreleased/` folder to the `$major.$minor.$patchVersion_YYYY-MM-DD` folder.
-4. Update the version in the following files (you can run `./dev/scripts/bump_versions.sh $version` if all get the same version):
-   - `package.json`
-   - `packages/design-system/package.json`
-   - `packages/eslint-config/package.json`
-   - `packages/web-pkg/package.json`
-   - `packages/web-client/package.json`
-   - `packages/web-test-helpers/package.json`
+4. Run `./dev/scripts/bump_versions.sh $version`. This script will bump the `package.json` files in all relevant packages.
 5. Commit and push your changes.
 6. Run `./dev/scripts/create_and_push_tags.sh`. This script will create and push tags for the main app as well as all packages that need to be released.
 7. After merging, wait for the CI to run on the merge commit.
@@ -39,3 +33,5 @@ The highest type before a new release determines the version update number, so i
 ### Next steps
 
 For oCIS the release assets need to be updated.
+
+<!-- TODO: add reference to docs on how to update Web in oCIS -->