Some general observations on the Wiki: this is a good start, but there are a number of things that need to be cleaned up. Mostly, the instructions I have read are unclear. There are many problems with non-standard and confusing usage of English.
(1) I started trying to edit the Wiki and immediately found there is some limit imposed on topic titles. Evidently, these titles must be at least 15 characters. Sorry, but this is stupid. A topic title like “Overview” is perfectly acceptable in software documentation. Your readers’ time is expensive – don’t ask them to read more text than necessary. If you want any serious community input, I strongly suggest you fix this immediately.
(2) Next, as I mentioned before on this thread, a task is an activity so task titles should be gerunds, i.e., you should have a topic entitled “Importing”, not “Import”.
(3) Next, I see many pages on the Wiki with titles including the word “issues”. In common English, “issues” now means “problems”, so all of these titles literally mean that MarginNote has many known problems. You should rename all of these pages to something more precise.
(3) Next, many page titles are questions. Questions are the language of a FAQ, not software documentation. All of these should be renamed to statements, not questions. I.e., " Q2 How can MarginNote3 import different types of documents?" should be renamed to “Importing Different Types of Documents”. So, get rid of all the question numbers (e.g., “Q2”) and make them statements.
(4) Next, on that page, Q2 How can MarginNote3 import different types of documents?, menu picks and UI elements should generally be emphasized in bold (e.g., the Share menu). This is for clarity and ease of understanding.
(5) Next, I find many arrow characters (→) used through the Wiki pages to indicate steps. This is confusing and not standard for technical documentation. The arrow character is normally used only for sub-menu items (e.g., Import → Add Documents from Files). If you want to indicate steps, use words like “Next”, “Then”, etc., or use numbers.
(6) Also, I would not put the version number of the application in the topic titles on the Wiki (e.g., “MarginNote3”). This is simply bad planning. What happens when MarginNote 4 is releated? Are you going to edit every single one of these Wiki pages?
(7) Next, for clarity, you should use the infinitive form of verbs that are directions to users. I.e., instead of “Add a document…”, you should write “To add a document…”.
(8) Next, including phrases like “follow the instructions” in front of an animated GIF is not adequate. You should explain the steps clearly in English. An animated GIF is not a set of instructions.
Ultimately, it is your responsibility as the software provider to explain the app’s operation clearly. Users/contributors cannot be expected to guess how all of these features work, and then document this in the Wiki.