diff --git a/iips/IIP-0009/iip-0009.md b/iips/IIP-0009/IIP-0009.md
similarity index 100%
rename from iips/IIP-0009/iip-0009.md
rename to iips/IIP-0009/IIP-0009.md
diff --git a/iips/IIP-0010/iip-0010.md b/iips/IIP-0010/IIP-0010.md
similarity index 99%
rename from iips/IIP-0010/iip-0010.md
rename to iips/IIP-0010/IIP-0010.md
index d98cb4d..d0d1b93 100644
--- a/iips/IIP-0010/iip-0010.md
+++ b/iips/IIP-0010/IIP-0010.md
@@ -39,7 +39,7 @@ Traditionally, answering these questions required either:
 
 Possible use cases exploiting `PackageMetadata` could be:
 
-1. Account Abstraction (planned) (see [IIP-0009](https://github.com/iotaledger/IIPs/blob/main/iips/IIP-0009/iip-0009.md)): Move code reads `PackageMetadata` to verify that a function is a valid authenticator and to obtain the account type it authenticates. This enables the `account` module to create `AuthenticatorInfoV1` instances that reference verified authenticator functions.
+1. Account Abstraction (planned) (see [IIP-0009](https://github.com/iotaledger/IIPs/blob/main/iips/IIP-0009/IIP-0009.md)): Move code reads `PackageMetadata` to verify that a function is a valid authenticator and to obtain the account type it authenticates. This enables the `account` module to create `AuthenticatorInfoV1` instances that reference verified authenticator functions.
 2. View Functions (planned) (see [IIP-0005](https://github.com/iotaledger/IIPs/blob/main/iips/IIP-0005/iip-0005.md)): Modules and clients can discover which functions are safe to call without state changes.
 3. Capability Verification: Modules can verify package capabilities before granting access.
 4. Function modifiers: Modules can parse functions of any package to check whether they are entry, private, etc.
@@ -64,7 +64,7 @@ The proposed Package Metadata model must adhere to the following constraints:
 
 To support `PackageMetadata`, we propose to modify part of the Move compilation, part of the publish/upgrade execution and the addition of a new module to the iota-framework.
 
-In the following, we are going to use the usage of Package Metadata within the IOTA Account Abstraction model (see [IIP-0009](https://github.com/iotaledger/IIPs/blob/main/iips/IIP-0009/iip-0009.md)), because that is a concrete use of the standard.
+In the following, we are going to use the usage of Package Metadata within the IOTA Account Abstraction model (see [IIP-0009](https://github.com/iotaledger/IIPs/blob/main/iips/IIP-0009/IIP-0009.md)), because that is a concrete use of the standard.
 
 ```
 ┌─────────────────────────────────────────────────────────────────┐
@@ -138,7 +138,7 @@ When a publish or upgrade transaction is executed, the protocol takes over. This
 
 ##### Verification
 
-During publish or upgrade, the protocol extracts `RuntimeModuleMetadata` from each module's bytecode using this the `IOTA_METADATA_KEY`, deserializes it, and verifies each attribute. For every attribute found, the protocol invokes the corresponding verifier. For authenticator attributes, for instance, this means calling `verify_authenticate_func_v1()`, which checks that the function has the correct visibility, parameter types, and return type (see [IIP-0009](https://github.com/iotaledger/IIPs/blob/main/iips/IIP-0009/iip-0009.md)).
+During publish or upgrade, the protocol extracts `RuntimeModuleMetadata` from each module's bytecode using this the `IOTA_METADATA_KEY`, deserializes it, and verifies each attribute. For every attribute found, the protocol invokes the corresponding verifier. For authenticator attributes, for instance, this means calling `verify_authenticate_func_v1()`, which checks that the function has the correct visibility, parameter types, and return type (see [IIP-0009](https://github.com/iotaledger/IIPs/blob/main/iips/IIP-0009/IIP-0009.md)).
 
 If any verification fails, the entire publish or upgrade transaction fails. User code cannot write to the `IOTA_METADATA_KEY` slot in a way that would bypass verification, because the verifier runs before execution completes, and any invalid metadata causes the transaction to fail.
 
@@ -308,7 +308,7 @@ Computing metadata IDs deterministically from package IDs means that any code, o
 
 ## Reference Implementation
 
-Main PR against the develop branch: https://github.com/iotaledger/iota/pull/9586. See [IIP-0009](https://github.com/iotaledger/IIPs/blob/main/iips/IIP-0009/iip-0009.md).
+Main PR against the develop branch: https://github.com/iotaledger/iota/pull/9586. See [IIP-0009](https://github.com/iotaledger/IIPs/blob/main/iips/IIP-0009/IIP-0009.md).
 
 ## Questions and Open Issues