update

Author: LogFlames

sbom-github.md

@@ -46,7 +46,7 @@ By the end of this post, you will clearly understand how to add SBOMs to your so
    This will generate a bom.xml file in the target directory. We use the `makeAggregateBom` goal to have a single sbom for all the modules of our project.
 
 2. (GitHub) Add the bom.xml and bom.json to your release script.
-   If you have the JReleaser YAML file, you can add the bom.xml to the files section of the release section.
+   If you have the JReleaser YAML file, you can add the bom.xml to the files section of the release section. This only affects the GitHub release.
 
    ```yaml
    files:
@@ -58,7 +58,7 @@ By the end of this post, you will clearly understand how to add SBOMs to your so
 
    This adds the bom.xml and bom.json to the release assets.
 
-3. (Maven Central) JReleaser can also upload the SBOMs to Maven Central from version 1.6.0.
+3. (Maven Central) JReleaser automatically uploads the SBOMs to Maven Central from version 1.6.0.
    If running JReleaser locally, make sure to use atleast version 1.6.0 and the SBOMs generated by `cyclonedx-maven-plugin` will be uploaded to Maven Central. 
    If using the `jreleaser/release-action` action, be aware that even if you use the latest version of the action it can pull different versions of JReleaser. If using atleast version 1.6.0 it will upload the SBOMs to Maven Central. 
    See example from `maven-lockfile` release action: