Merge pull request #27 from malfisya/patch-1

README.md: Fix incorrect or dead url

README.md

@@ -36,7 +36,7 @@ Paste a suitable excerpt of the above to e.g. https://bpa.st and link to it in t
 
 ## Difference to alternatives
 
-As the original author of [clr-boot-manager](https://github.com/intel/clr-boot-manager) it needs listing here as "prior art", in terms of synchronising `$BOOT` and `/usr/lib/kernel` for type 1 BLS entries.
+As the original author of [clr-boot-manager](https://github.com/clearlinux/clr-boot-manager) it needs listing here as "prior art", in terms of synchronising `$BOOT` and `/usr/lib/kernel` for type 1 BLS entries.
 
 However the original design has a number of weaknesses and doesn't provide a sane schema for the automated discovery of kernel assets without a compile-time vendor prefix.
 
@@ -45,7 +45,7 @@ In a similar vein, [kernel-install](https://www.freedesktop.org/software/systemd
 Additionally `kernel-install` is designed to be a one-shot utility invoked by packaging triggers (or users) rather than a more contained facility to synchronise the target `ESP` (or `$BOOT`) with the expected state as provided by the final package-managed state.
 
 
-In the scope of [Serpent OS](https://getsol.us) and [Solus](https://getsol.us) - prebuilt initrds have been in use for years with great success. Given the requirement for both distributions to function correctly in dual-boot and non-appliance use cases, a `.uki` isn't going to permit our use case of generating dynamic cmdlines and shipping pre-signed assets.
+In the scope of [Serpent OS](https://serpentos.com/) and [Solus](https://getsol.us) - prebuilt initrds have been in use for years with great success. Given the requirement for both distributions to function correctly in dual-boot and non-appliance use cases, a `.uki` isn't going to permit our use case of generating dynamic cmdlines and shipping pre-signed assets.
 
 ## Filesystem layout