Merge pull request #4 from ensdomains/greg/readme

Fix link in readme

contracts/README.md

@@ -5,7 +5,7 @@ Currently this repository hosts Proof-of-Concept contracts for ENSv2. See the [E
 At present the following contracts are implemented:
  - [RegistryDatastore](src/registry/RegistryDatastore.sol) - an implementation of the registry datastore defined in the design doc. All registry contracts must use a singleton instance of the datastore for storage of subregistry and resolver addresses.
  - [ERC1155Singleton](src/registry/ERC1155Singleton.sol) - an implementation of the ERC1155 standard that permits only a single token per token ID. This saves on gas costs for storage while also permitting easy implementation of an `ownerOf` function.
- - [BaseRegistry][src/registry/BaseRegistry.sol] - an implementation of the registry defined in the design doc, to be used as a base class for custom implementations.
+ - [BaseRegistry](src/registry/BaseRegistry.sol) - an implementation of the registry defined in the design doc, to be used as a base class for custom implementations.
  - [RootRegistry](src/registry/RootRegistry.sol) - an implementation of an ENSv2 registry to be used as the root of the name hierarchy. Owned by a single admin account that can authorise others to create and update TLDs. Supports locking TLDs so they cannot be further modified.
  - [ETHRegistry](src/registry/ETHRegistry.sol) - a basic implementation of an ENSv2 .eth registry. Supports locking TLDs and name expirations; when a name is expired, its resolver and subregistry addresses are zeroed out. User registrations and renewals are expected to occur via a controller contract that handles payments etc, just as in ENSv1.
  - [UserRegistry](src/registry/UserRegistry.sol) - a sample implementation of a standardized user registry contract. Supports locking subnames.