refactor: add concurrency group and tweak some names

.github/workflows/build-38.yml

@@ -1,4 +1,4 @@
-name: ublue nvidia 38
+name: ublue hwe 38
 on:
   pull_request:
   merge_group:

.github/workflows/build-39.yml

@@ -1,4 +1,4 @@
-name: ublue nvidia 39
+name: ublue hwe 39
 on:
   pull_request:
   merge_group:

.github/workflows/reusable-build.yml

@@ -9,6 +9,10 @@ on:
 env:
   IMAGE_REGISTRY: ghcr.io/${{ github.repository_owner }}
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref || github.run_id }}-${{ inputs.fedora_version }}
+  cancel-in-progress: true
+
 jobs:
   build_ublue:
     name: hwe

README.md

@@ -1,12 +1,12 @@
-# Nvidia
+# HWE
 
-[![build-38](https://github.com/ublue-os/nvidia/actions/workflows/build-38.yml/badge.svg)](https://github.com/ublue-os/nvidia/actions/workflows/build-38.yml) [![build-39](https://github.com/ublue-os/nvidia/actions/workflows/build-39.yml/badge.svg)](https://github.com/ublue-os/nvidia/actions/workflows/build-39.yml)
+[![build-38](https://github.com/ublue-os/hwe/actions/workflows/build-38.yml/badge.svg)](https://github.com/ublue-os/hwe/actions/workflows/build-38.yml) [![build-39](https://github.com/ublue-os/hwe/actions/workflows/build-39.yml/badge.svg)](https://github.com/ublue-os/hwe/actions/workflows/build-39.yml)
 
-The purpose of these images is to provide [community Fedora images](https://github.com/ublue-os/main) with Nvidia drivers built-in. This approach can lead to greater reliability as failures can be caught at the build level instead of the client machine. This also allows for individual sets of images for each series of Nvidia drivers, allowing users to remain current with their OS but on an older, known working driver. Performance regression with a recent driver update? Reboot into a known-working driver after one command. That's the goal!
+The purpose of these images is to provide [community Fedora images](https://github.com/ublue-os/main) with hardware enablement (ASUS and Surface) and Nvidia. This approach can lead to greater reliability as failures can be caught at the build level instead of the client machine. This also allows for individual sets of images for each series of Nvidia drivers, allowing users to remain current with their OS but on an older, known working driver. Performance regression with a recent driver update? Reboot into a known-working driver after one command. That's the goal!
 
 # Documentation
 
 - [Main website and documentation](https://universal-blue.org)
-- [Documentation for these images](https://universal-blue.org/images/nvidia)
+- [Documentation for these images](https://universal-blue.org/images/hwe)
 - [Installation](https://universal-blue.org/installation/) - follow this for clean installation
 - [Rebase instructions](https://universal-blue.org/images/) - follow this if you want to switch to another image.