Minor suggestions to the Identity Resolver:

### Tool Name
I suggest keeping the tool name as "Identity Resolver" instead of "Decentralized Identifier".

### Info button in the tool landing page
The tool landing page has a `...` button which still inclues a place holder. This could be changed to:
> Decentralized Identifiers
---
> A Decentralized Identifier, or DID, is a unique identifier that is tied to a subject. This subject can be anything, like a person, an organization, an IoT device, or even an object. The identifier can be used by the subject to identify themselves through a digital format, providing a basis for online identification. An Example for a DID is:
>
> <b>did:iota:3TT7QsmESw1dcboV2oVTAuJbbxaVYAThexZFct2z5Q2d</b>
>
> The first three characters indicate that the DID standard from W3C must be used to resolve the identifier. It is followed by a unique method name, in our case iota, to indicate that the IOTA method is used. The last part contains set of random characters that are unique per identity, this makes the identity unique and makes sure every identity resolves to a unique DID Document.
>
> This DID can be resolved into its associated DID Document. This document contains data such as public keys, enabling the holder to prove ownership over their personal data, but also URIs that link to public information about the identity.
>
>Visit the [identity wiki](https://wiki.iota.org/identity.rs/decentralized_identifiers/create) to get started and create your own DID.

### Info button in the `General` section
The tool details page has a `i` icon next to the `General` section. This button should be removed, since no explanation is needed for its content.

### Info button in the `Content` section
The tool details page has a `Content` section, this section should be renamed to `Current DID Document` instead. It also has a `i` button which shows a place holder. The content can be changed to:

> Current DID Document
---
>This section includes the latest state of the DID document.
>A DID Document mostly contains two important pieces of data: public keys and services. The public keys can be used to prove ownership over the identity, by cryptographically signing something with the associated private key. The public key can be used to verify that the identity subject signed the data and therefore controls the private key. Ownership over the private keys, therefore, proves ownership over the identity. This also means that it is very important to keep the private keys safe and secure. In addition, the public keys allow users to send encrypted data to the identity, using their public key, that only the identity owner can decrypt.
>
> Note: The metadata of the document are removed from the resolution.

### Info button in the `History` section
The tool details page has a `History` section, This section should have an `i` button with the following content:

> Document History
---
>This section includes all valid <em>integration</em> and <em>diff</em> messages that were published for this DID.
>Read more about DID Messages [here](https://wiki.iota.org/identity.rs/advanced/did_messages#did-messages).
>
>By default, only integration messages are shown. Click on the <em>diff icon</em> to expand the diff messages published for that integration message.
>
> The <em>Doc</em> view shows a constructed DID document. This view is helpful for diff messages since they only publish the difference to the last document instead of an entire document. You can still see the raw content of the message by using the `Msg` view.
>
> Messages can be compared by selecting a previous message from the drop-down menu. Notice that diff messages are only available if they were expanded first. Also, diff messages are usually only useful to compare in <em>Doc</em> view.