README: Fix fragments

README.md

@@ -7,7 +7,7 @@ There are two variants of this project:
 
 - OpenEUICC: The full-fledged privileged variant.
   - Due to its privilege requirement, OpenEUICC must be placed inside `/system/priv-app` and be signed with the platform certificate.
-  - The preferred way to including OpenEUICC in a system image is to [build it along with AOSP](#building--aosp-).
+  - The preferred way to including OpenEUICC in a system image is to [build it along with AOSP](#building-aosp).
 - EasyEUICC: Unprivileged version that can run as a user app.
   - Due to obvious security requirements, EasyEUICC is only able to access eSIM chips whose [ARF/ARA](https://source.android.com/docs/core/connect/uicc#arf) contains the hash of EasyEUICC's signing certificate.
   - Prebuilt release-mode EasyEUICC apks can be downloaded [here](https://gitea.angry.im/PeterCxy/OpenEUICC/releases)
@@ -56,7 +56,7 @@ There are two ways to include OpenEUICC in your AOSP-based system image:
    - If inclusion in `manifest.xml` is required, remember to set the `sync-s` option to clone submodules.
    - The module name is `OpenEUICC`. You can include it in `PRODUCT_PACKAGES`, or simply build it standalone using `mm`.
    - Compilation of this project is **only** tested against the latest AOSP release version. The app itself should be compatible with older AOSP versions, but the source may not compile against an older AOSP source tree.
-2. If compilation against AOSP source tree is not possible, consider [building with gradle](#building--gradle-) and import the apk as a prebuilt.
+2. If compilation against AOSP source tree is not possible, consider [building with gradle](#building-gradle) and import the apk as a prebuilt.
    - No official `Android.bp` is provided for this case but it should be straightforward to write.
    - You might want to include `privapp_whitelist_im.angry.openeuicc.xml` as well.