diff --git a/110.md b/110.md
index 28bd314..d96b47b 100644
--- a/110.md
+++ b/110.md
@@ -1,26 +1,26 @@
 NIP-110
 =======
 
-MIT License
+License tag
 -----------
 
 `draft` `optional` `author:degenrocket`
 
-This NIP defines how to add an MIT license to Nostr events.
+This NIP defines how to add licenses to Nostr events.
 
-### Problem
+### Problems
 
-Currently, the Nostr ecosystem is growing in a very friendly environment, but once the environment will change to hostile, relays and clients can face legal responsibilities for distributing the copyright-protected content.
+Currently, the Nostr ecosystem is growing in a very friendly environment, but once the environment will change to hostile, relays and clients can face legal responsibilities for distributing the copyright-protected content. At the moment of writing, a user who signs a Nostr event doesn't give an explicit permission for his content to be distributed without any restriction.
 
-At the moment of writing, a user who signs a Nostr event doesn't give an explicit permission for his content to be distributed without any restriction.
+Another problem is that some users want to use different licenses for different content like text and media files.
 
 ### Solution
 
-The easiest solution for this problem is to add an MIT license to each signed event in accordance with the [SPASM](https://github.com/degenrocket/spasm) specification.
+The easiest solution for this problem is to add a license to each signed event in accordance with the [SPASM](https://github.com/degenrocket/spasm) specification.
 
-Then relays and clients can check whether events have an MIT license and choose whether to display/distribute such events or not.
+Then relays and clients can check whether events have an MIT license or any other license and choose whether to display/distribute such events or not.
 
-While adding a dedicated license field (`"license":"MIT"`) would be ideal, the easiest solution with backwards-compatibility is to add a license as a tag.
+While adding a dedicated license field (e.g., `"license":"MIT"`) would be ideal, the easiest solution with backwards-compatibility is to add a license as a tag.
 
 ```js
 tags: [