Various additions and fixes

src/content/docs/Artist entry page.mdx

@@ -146,11 +146,11 @@ Tags can be removed by any trusted user, regardless who added and voted for the
 
 #### Official links
 
-- Links from categories "official" and "commercial" are shown as one list, alphabetically sorted.
+- Links from the "official" and "commercial" categories are shown as one list, alphabetically sorted.
 
 #### Unofficial links
 
-- Links from categories "reference" and "other" are shown as one list, alphabetically sorted.
+- Links from the "reference" and "other" categories are shown as one list, alphabetically sorted.
 
 #### Base voicebank
 

src/content/docs/Artist types.mdx

@@ -13,13 +13,13 @@ Be careful when changing artist's type when that artist already has songs/albums
 
 Guidelines for splitting voicebank entries is documented on [the FAQ-page](/docs/pinned/vocadb-editing-faq#should-a-vocaloid-with-multiple-voicebanks-be-split-into-multiple-entries).
 
-### [Vocaloid](https://vocadb.net/T/4857)
+### [VOCALOID](https://vocadb.net/T/4857)
 
 The Vocaloid type is reserved only for the voicebanks based on the Vocaloid desktop software (regardless of version). Upgraded versions such as appends use this type as well.
 
 ### [UTAU](https://vocadb.net/T/447/utau)
 
-UTAU is identical to the Vocaloid type, except for the UTAU software. Official appends and other upgrades/extensions to voicebanks use this type as well.
+Functions similarly to the Vocaloid type, but for the UTAU software. Official appends and other upgrades/extensions to voicebanks use this type as well.
 
 ### [CeVIO](https://vocadb.net/T/2838)
 
@@ -41,7 +41,7 @@ VoiSona (formerly known as CeVIO Pro (仮)) is a voice synthesizer product devel
 
 TODO
 
-### [Voiceroid](https://vocadb.net/T/486)
+### [VOICEROID](https://vocadb.net/T/486)
 
 A speech synthesizer program developed by AH-Software, released on December 4, 2009. Despite being separate programs, its name is derived from "VOCALOID"; however, while VOCALOID is meant for singing, VOICEROID is meant for speaking.
 

src/content/docs/Artist verification.mdx

@@ -12,45 +12,45 @@ If you are an artist working with music production, you may request your
 Other roles such as illustrator, animator and mixer are also included.
 
 **The requirement is that you need to have at least one song entry on
-VocaDB**. This can be original song, cover, remix or music PV, as long
+VocaDB**. This can be an original song, cover, remix or music PV, as long
 as it features vocals synths.
 
 ## Why?
 
-As a verified artist your user account name is **displayed** on the
-artist entry page, and vice versa. You also gain access to more
-privileges regarding your artist entry. You may mark your artist entry
-as **approved**, preventing new users from editing that entry. You may
-also **remove tags** associated with your entry and provide **personal
-descriptions** for your albums and songs.
+As a verified artist, your user account name is **displayed** on the
+artist entry page, and vice versa. You also gain access to the following actions:
+- Marking your artist entry as **approved**, preventing new users from editing that entry. 
+- **Removing tags** associated with your entry 
+- Providing **[personal descriptions](/docs/songs/song-entry-page#artists-personal-description)** for your albums and songs.
+- Uploading song files (such as .mp3s) directly to VocaDB
 
-Edits by verified artists are by default explanatory/trusted when
+Edits by verified artists are, by default, considered trusted when
 editing their own entries. For example, as a verified artist you may
 mark the specific voicebank used without further explaining it - we
 trust that you know what you're doing. **This means less work for both
 you and the moderation team**.
 
-## How?
+## How can I get verified?
 
-You can do this by
-[submitting a verification request on VocaDB](https://vocadb.net/User/RequestVerification).
+By [submitting a verification request on VocaDB](https://vocadb.net/User/RequestVerification).
 **You need to provide some way to prove that you are the artist**.
+Some examples of accepted methods of verification: 
 
-- Post a tweet saying you want your account verified on VocaDB. To do this, use your artist Twitter account, to create a Tweet linking to your VocaDB **user** account (instead of your artist page).
+- Make a post on your official social media (Twitter, YouTube, etc.) saying you want your account verified on VocaDB. The post should link to your VocaDB **user** account (https://vocadb.net/Profile/), not your artist page.
 
 For example: ![Artist verification example](/images/verification.PNG "Artist verification example")
 
 - Temporary profile/video description texts work as well:
 
 > My VocaDB account: https://vocadb.net/Profile/...
 
-- The official website you're using for the verification must be linked to your artist entry. 
+- The official website you're using for verification must be linked to your artist entry. 
 
 - Another way is to send a message to a site moderator. [Other contacting options](/docs/footer/contact).
 
-- Your request will be rejected without proper proof! **Screenshots are not accepted.** Tweets or other public messages do not count, if they are not about artist verification.
+- Your request will be **rejected** without proper proof! **Screenshots are not accepted.** Tweets or other public messages do not count, if they are not about artist verification.
 
-Multiple artist entries (for example, circle or UTAU voicebank) can be
+Multiple artist entries (for example, circles or UTAU voicebanks) can be
 connected to the same user account (please mention this when submitting
 the verification request).
 

src/content/docs/Choosing the main picture for artist entries.mdx

@@ -19,7 +19,7 @@ Sorted in order of importance (the first rule that matches should be used).
 
 * Picture of the artist, but **only** if publicly available on artist's website/online profile (twitter, Facebook etc.).
     * Photo taken by a fan or posted on artist's private profile should not be used, 
-because it might be considered inappropriate.
+because it might be considered a breach of privacy.
 * Official illustration of the artist
 * Official logo
 * Another picture officially associated with the artist

src/content/docs/Content removal guidelines.mdx

@@ -31,7 +31,7 @@ Content removal requests **must always be verified** in some way. Having a [veri
 
         * Cover entries are an exception
 
-    You can alternatively request the [do not reupload -tag](https://vocadb.net/T/1695/do-not-reupload) to your artist/song entries, which disables existing or new reprint links.
+    You can alternatively request the [do not reupload](https://vocadb.net/T/1695/do-not-reupload) tag be added your artist/song entries, which disables existing or new reprint links.
 
 ## Album entry removal checklist:
 

src/content/docs/Discussion rules.mdx

@@ -18,7 +18,7 @@ _Moderators can edit/remove comments that do not adhere to these rules._
 
 Engage in **mature and thoughtful** discussions. **Reactionary, low-effort, or provoking** comments are **not allowed**. Contributions should be **respectful** and aimed at promoting meaningful conversation.
 
-It is encouraged that you try to include all information in a single comment rather than making multiple.
+It is encouraged that you include all information in a single comment rather than making multiple.
 Posting **identical/near-identical** comments on multiple entries will result in them being **deleted**.
 
 ### Other

src/content/docs/Merging entries.mdx

@@ -15,7 +15,7 @@ This includes the following:
 * Song votes (favorites and likes)
 * Tag votes
 
-**The process cannot be reversed automatically** - to undo a merge you'll have to restore the old source entry and edit all references manually. Some properties such as song and tag votes **cannot be restored**. Therefore you need to be **especially careful** before proceeding with the merge: make sure that the entries really need to be merged.
+**The process cannot be reversed automatically** - to undo a merge you'll have to restore the old source entry and edit all references manually. Some properties such as song and tag votes **cannot be restored**. Therefore, you need to be **especially careful** before proceeding with the merge: make sure that the entries really need to be merged.
 
 Because undoing a merge can be a great deal of work, it is restricted to Trusted Users and above. If you notice a duplicate entry but can't perform the merge yourself, leave an entry report (including the other duplicate).
 

src/content/docs/Staff roles.mdx

@@ -81,4 +81,4 @@ Responsibilities:
 
 ### Other roles
 
-Previous staff members: [riipah](https://vocadb.net/Profile/riipah) (founder), [MrMeteor](https://vocadb.net/Profile/MrMeteor), [ycanardeau](https://vocadb.net/Profile/ycanardeau)
+Former staff members: [riipah](https://vocadb.net/Profile/riipah) (founder), [MrMeteor](https://vocadb.net/Profile/MrMeteor), [ycanardeau](https://vocadb.net/Profile/ycanardeau)

src/content/docs/Tags.mdx

@@ -27,15 +27,19 @@ Adding tag votes to objective tags is redundant, unless there is a need to "high
 
 ## Creating and editing tags
 
-Every tag should reflect some well-defined concept. Avoid overly specific tags that only apply to one or two entries.
+Every tag should reflect some well-defined concept. For this reason, tag entries **must** have:
+- External links (for verification that the concept is recognized / well defined)
+- A description (to clearly state the tag's purpose)
+- A category 
+- Usage on **at least one** entry (besides for tags of the "Copyright" category, whose [requirements are different](/docs/secondary-entry-types/tags#copyrights)).
+
+Furthermore, tags applied to album or artist entries should be used on a sizable portion of the album/artist's songs. Additionally, do not add tags based solely on album art or an artist's profile picture.
 
 Tags should add **new information** to the entry. Creating "derived tags" that replicate information from the existing fields is **discouraged**, unless the tag is useful enough (see the tag purposes below) and there is no easy/reliable way to search/list the relevant information ([duet](https://vocadb.net/T/3180) for example).
 
 Generally tags should not be created or used for tracking **visual details**. This includes the creation of visual detail tags in the Vocalist category.
 
-All tags require description and a tag category. Additionally, it's recommended to locate a fitting tag parent and/or related tags. If tags have the same parent tag, specifying them as related tags is redundant.
-
-Tag description should describe the tag concept in clear English language. For normal tags, skip generic usage instructions such as "tag for albums/artist/songs...". Use "Valid for" -restrictions instead.
+A tag's description should explain its intended usage in clear English language. For normal tags, skip generic usage instructions such as "tag for albums/artist/songs...". Use "Valid for" restrictions instead.
 
 Including external links to objective sources, such as Wikipedia, is recommended.
 
@@ -97,6 +101,10 @@ Common exceptions:
 - Tags for the general PV style ([comics PV](https://vocadb.net/T/3304/comics-pv))
 - Tags for information/meta-details ([mismatching vocalist PV](https://vocadb.net/T/4879/mismatching-vocalist-pv))
 
+
+### Composition
+Tags related to the [composition](https://en.wikipedia.org/wiki/Musical_composition) of a song.
+
 ### Copyrights
 
 Tags related to any sort of intellectual property (IP).
@@ -110,6 +118,12 @@ Copyright tags can be created for a few reasons:
 
 Avoid creating tags for C and D if they do not apply to at least 5 song entries.
 
+
+### Derivative 
+Mostly for fanmade (unofficial) voice synth voice configurations (derivatives).
+
+By default, derivative characters (fanmade or official) **without their own voicebank** should be indicated with tags instead of artist entries.
+
 ### Distribution
 
 Tags related to the album/song distribution.
@@ -130,7 +144,7 @@ Games with soundtracks created specifically for the game should be under the Cop
 
 ### Instruments
 
-Tags that describe the [musical instrument](https://en.wikipedia.org/wiki/Musical_instrument).
+Tags for tracking [musical instruments](https://en.wikipedia.org/wiki/Musical_instrument) used in songs.
 
 ### Jobs
 
@@ -160,7 +174,7 @@ Information relating to a song's origin, for example, that it was produced in [F
 
 ### Subjective
 
-Subjective theme tags.
+Subjective theme tags, generally related to the emotional "feel" or "tone" of a song.
 
 ### Themes
 

src/content/docs/Trusted users.mdx

@@ -28,12 +28,12 @@ Here are some things to keep in mind:
 * Avoid fights or personal insults in the public entry comment sections. Personal arguments are to be resolved elsewhere. AKA no drama.
 * Communicate! If you're unsure, post a question in the comments. If you find something to be improved, or disagree with our rules, post your opinion in the comments (but avoid unnecessary, pointless arguing). Note that ignoring others, (especially staff members), doesn't work in the long run. If you're being harassed, message a staff member.
 * The [entry reports](https://vocadb.net/Admin/ViewEntryReports) page is for reports themselves; they are **NOT just notifications**. The exclaimation point and number under the "Account" menu are there to let you know that there are active reports that need to be addressed. If you dislike this feature, you may use the [Stylus](https://github.com/openstyles/stylus/) extension and install [this script](https://userstyles.world/style/19593/hide-vdb-notifs) by Shiroizu. **Do not close them** unless they have been fixed or otherwise addressed. 
-* The limiting permissions that trusted users have are intended as a way to quickly respond to major issues like spam or vandalism if no moderators or admins are available. Besides those cases, trusted users should generally not use the limiting permission.
+* The limiting permissions that trusted users have are intended as a way to quickly respond to major issues such as spam or vandalism if no moderators or admins are available. Besides those cases, trusted users should generally not use the limiting permission.
 
 Also see the [editing FAQ](/docs/pinned/vocadb-editing-faq) and [User groups](/docs/documentation/user-groups).
 
 ## How to become trusted user?
 
-There is no specific criteria for becoming a trusted user. It is based on the time spent on the website, number and (especially) quality of edits. A small number of detailed edits can be reason enough for becoming trusted. Communication also matters. We expect trusted users to be sufficiently respectful, avoid arguments with other users, and ask someone senior if they're unsure of something. That also means taking responsibility of correcting any mistakes with your edits when someone points them out.
+There are no specific criteria for becoming a trusted user. It is based on time spent on the website, quantity, and (especially) quality of edits. A small number of detailed edits can qualify a user for promotion. Communication also matters; we expect trusted users to be respectful, avoid arguments with other users, and ask someone senior if they're unsure of something. This also means taking responsibility for correcting any mistakes with your edits when someone points them out.
 
 Please don't ask us to promote you to trusted. Eventually a staff member (moderator or administrator) will notice your edits, make a short review and promote you if they're satisfied. If they're unsure, they will contact you and/or other staff members first.

src/content/docs/User groups.mdx

@@ -69,7 +69,7 @@ Users with verified email can log in by using their email address instead of the
 
 ### Staff
 
-Label for administrators and moderators. Also displayed for users with the "Designated staff member" -permission enabled.
+Label for administrators and moderators. Also displayed for users with the "Designated staff member" permission enabled.
 
 ### VocaDB veteran
 

src/content/docs/UtaiteDB Songs.mdx

@@ -40,7 +40,7 @@ When an artist participates as a band/unit with others under one name, the song
 
 ## Song types
 
-UtaiteDB uses the same song type classification as VocaDB, with some modifications. Please see the wiki entry page for [song types](/docs/songs/song-entry-editing#song-type).
+UtaiteDB uses a slightly modified version of the song types from VocaDB. Please see the wiki entry page for [song types](/docs/songs/song-entry-editing#song-type).
 
 ## Song embeds and PVs
 

src/content/docs/VocaDB editing FAQ.mdx

@@ -39,7 +39,7 @@ Documented on [Song entry editing](/docs/songs/song-entry-editing#cover).
 
 ### I think that a song is using an append, or another version than indicated, but can't confirm. Which voicebank should I use?
 
-In general you should use the voicebank indicated by the artist. If you have a strong reason to believe that the voicebank is an append or other variation, such as Vocaloid 3 upgrade of the voicebank, you may add that voicebank instead, but please mention that in the edit notes, song notes or comments.
+In general you should use the voicebank indicated by the artist. If you have a strong reason to believe that the voicebank is an append or other variation, such as a Vocaloid 3 upgrade of the voicebank, you may add that voicebank instead, but please mention that in the edit notes, song notes or comments.
 
 Rationale: all information on VocaDB should be verifiable; there should ideally be a clear way to confirm it by checking an official source.
 

src/content/docs/VocaDB feature requests.mdx

@@ -7,9 +7,9 @@ tags: ["development", "documentation", "feature requests", "github", "vocadb"]
 
 ## Contributing to VocaDB
 
-VocaDB's new feature development is tracked as [GitHub issues](https://github.com/VocaDB/vocadb/issues) on the [VocaDB GitHub](https://github.com/VocaDB/vocadb). This includes bug fixes. If VocaDB is lacking a feature that you are expecting, you may [submit a feature request](https://github.com/VocaDB/vocadb/issues/new/choose) on GitHub. Please use the search to make sure that the feature has not already been requested. If the feature request has already been submitted by another user, you may give a "thumbs up" vote on the issue to help us prioritize it further.
+The development of new features (and bugfixes) is tracked via [GitHub issues](https://github.com/VocaDB/vocadb/issues) on the [VocaDB GitHub](https://github.com/VocaDB/vocadb). If VocaDB is lacking a feature that you expect, you may [submit a feature request](https://github.com/VocaDB/vocadb/issues/new/choose) on GitHub. Please use the search to make sure that the feature has not already been requested. If the feature request has already been submitted by another user, you may give a "thumbs up" vote on the issue to help us prioritize it further.
 
-When submitting a new feature request/issue, make sure you include as much information as possible. You also need to explain why do you need that specific feature: what are the use cases? Explain step by step how would you imagine the feature would work.
+When submitting a new feature request/issue, make sure you include as much information as possible. You also need to explain why you feel that specific feature is useful. Explain step by step how would you imagine the feature would work and the benefits of implementing it.
 
 Please understand that unless the feature is extremely simple or requested by a very large number of users, it will take a long time for it to be implemented. Implementing a single feature may take anything from 1 hour to many weeks of concentrated work.
 
@@ -19,4 +19,4 @@ Please understand that unless the feature is extremely simple or requested by a
 
 Take a look at the code and instructions in [this README](https://github.com/VocaDB/vocadb#readme) on the [VocaDB GitHub](https://github.com/VocaDB/vocadb).
 
-Any bugs and change requests are to be reported on the VocaDB GitHub, on the issues tab. If you think you could help, take a look at the list of reported issues, create a fork and you can fix it there and create a pull request back to the main repository.
+Any bugs and change requests are to be reported on the VocaDB GitHub as issues. If you think you could help, take a look at the list of reported issues, create a fork, fix the issue, and create a pull request back to the main repository.