Fix links

Author: glatzert

docfx/docs/profile-config.md

@@ -59,7 +59,7 @@ The profile selection process will run the identifier validation and only select
 ```
 
 A profile for device-attest-01 challenges could look like this:
-Device-Attest-01 is a little bit more involved, since it allows remote validation via an [POST reqeuest](./AboutDeviceAttest.md) and needs to be configured with the Apple root certificate.
+Device-Attest-01 is a little bit more involved, since it allows remote validation via an [POST reqeuest](./device-attest.md) and needs to be configured with the Apple root certificate.
 Currently, the device-attest-01 challenge is not standardized, so this profile is experimental and may change in the future - also it only supports the Apple device-attest-01 challenges.
 
 If you are interested in android support or tpm support, please open an issue on the GitHub repository.

docfx/index.md

@@ -19,7 +19,7 @@ It needs an Microsoft ADCS for certificate issuance, that allows auto-enrollment
 - Challenge types: `http-01`, `dns-01`, `tls-alpn-01`, `device-attest-01` (experimental, until standardized, Apple only currently, [more Information](./docs/device-attest.md)) 
 - ExternalAccountBinding (EAB) support ([more Information](./docs/eab.md))
 - Identifier types: `dns` ([RFC 8555](https://www.rfc-editor.org/rfc/rfc8555#section-9.7.7)), `ip` ([RFC 8738](https://www.rfc-editor.org/rfc/rfc8738)), `permanent-identifier` (experimental, [Draft](https://www.ietf.org/archive/id/draft-acme-device-attest-04.html))
-- [Profiles](./docs/AboutProfiles.md) 'automatic' and ['client selected'](https://datatracker.ietf.org/doc/draft-aaron-acme-profiles/01/), which allow to define different settings for different identifiers, e.g. different templates or CA servers.
+- [Profiles](./docs/profile-config.md) 'automatic' and ['client selected'](https://datatracker.ietf.org/doc/draft-aaron-acme-profiles/01/), which allow to define different settings for different identifiers, e.g. different templates or CA servers.
 
 ## License