Merge pull request #480 from RafaelGB/imed-docu-branch

Imed docu branch

Author: imed-ghomari

docs/docs/features/Columns.md

@@ -14,15 +14,15 @@ The plugin can grab all the metadata from all the files included in the selected
 
 ### Add From Template
 
-The plugin can look at only one file (as a template), and grab only this file's metadata as columns. The list of files to choose from is provided from the used source and can be found in the database setting under `select file as column template`.
+The plugin can look at only one file (as a template), and grab only this file's metadata as columns. The list of files to choose from is provided from the used source and can be found in the database settings under `select file as column template`.
 
 ## Hiding
 
 You can hide the columns while keeping the underlying metadata by using the column menu or by pressing the `+` button, where you'll see a list of all the columns (hidden or not).
 
 ## Removing
 
-You can remove the column and remove its underlying metadata by using the column menu. Make sure to enable `configuration about columns > remove fields` in the plugin setting or in the database settings.
+You can remove the column and remove its underlying metadata by using the column menu. Make sure to enable `configuration about columns > remove fields` in the plugin global settings or in the database settings.
 
 ## Resizing
 

docs/docs/features/Formulas.md

@@ -20,5 +20,5 @@ To use an exposed variable, use the `${}` syntax. For example, to get the value
 
 The root object `db` has the following functions:
 
-- `js` : execute a javascript function that you previously defined in the `js` folder of your table in the database or plugin settings. (I.E.: `db.js.myFunction( arg1, arg2)`)
+- `js` : execute a javascript function that you previously defined in the `js` folder of your table in the database or plugin global settings. (I.E.: `db.js.myFunction( arg1, arg2)`)
 

docs/docs/features/Notes.md

@@ -10,13 +10,13 @@ You have to choose a template in the bottom bar before creating the note. You ca
 
 ## Deleting & Renaming Notes
 
-You can use the dots to the right of every row, to bring up a menu where you can delete and rename the note associated with the row.
+You can click on the numbers to the right of every row, to bring up a menu where you can delete and rename the note associated with the row.
 
 ## Moving Notes Based on Metadata
 
 The database will watch for changes in the select property column and create folders for each option present. The notes will be placed under the corresponding folder based on the option chosen. 
 
-You can choose one or many select properties by which this rule will run. If you choose more than one, the folders will be nested and the nesting order will follow the order by which the select properties are added in the database setting. For example *"select1/select2/select3"*. This setting can be found under `configuration about columns > Columns to group by`.
+You can choose one or many select properties by which this rule will run. If you choose more than one, the folders will be nested and the nesting order will follow the order by which the select properties are added in the database settings. For example *"select1/select2/select3"*. This setting can be found under `configuration about columns > Columns to group by`.
 
 You have additional settings to customize this rule under `configuration about columns` in the database settings :
 

docs/docs/features/Properties.md

@@ -1,14 +1,14 @@
 ## Types
 
-- **Text**: this property support markdown, links, and tags. If you're using links you can enable alias in the column settings or in the plugin settings ;
+- **Text**: this property support markdown, links, and tags. If you're using links you can enable alias in the column settings or in the plugin global settings ;
 - **Number**: this property only accepts numbers ;
 - **Checkbox**: this property is represented by `true/false` in the underlying markdown ;
 - **Date**: this property accepts dates. The default format is `yyyy-MM-dd`, but it can be changed in the plugin or database settings under `editing engine section > Date format` ;
 - **Time**: this property accepts time. The default format is `yyyy-MM-dd HH:mm:ss`, but it can be changed in the plugin or database settings under `editing engine section > Datetime format` ;
-- **Select**: this property accepts from a list of options you define. Colors are attributed automatically, though you can change them in the column setting. Furthermore, when removing the select option in the setting, it is also removed from the note's metadata ;
+- **Select**: this property accepts from a list of options you define. Colors are attributed automatically, though you can change them in the column settings. Furthermore, when removing the select option in the setting, it is also removed from the note's metadata ;
 - **Tags**: similar to the previous property, but instead of only selecting one option, you can select multiples options per cell ;
 - **Formulas**: property that accepts js code to return dynamic values in function of your code. See the [Formulas](/obsidian-db-folder/features/Formulas/) section for more details.
-- **Image**: you can embed images in the `text` property in this format `![[image]]`. Make sure to enable `media links` in the column setting and adjust the dimensions too ;
+- **Image**: you can embed images in the `text` property in this format `![[image]]`. Make sure to enable `media links` in the column settings and adjust the dimensions too ;
 - **Created time**: this column can be added only once from the database settings and will display the created time of the row ;
 - **Modified time**: this column can be added only once from the database settings and will display the last modified time of the row ;
 - **Tasks**: this column can be added only once from the database settings and will display the task of the given file. You can also choose to hide the completed tasks in the column settings ;
@@ -21,11 +21,11 @@
 
 The plugin works with YAML and dataview inline fields, but by default, it looks for metadata in YAML. To make it work with inline fields, you have two options :
 
-- You can toggle `enable inline field as default` in database or plugin setting, and you can choose between putting the inline fields at the top or at the bottom of the file ;
+- You can toggle `enable inline field as default` in database or plugin global settings, and you can choose between putting the inline fields at the top or at the bottom of the file ;
 - Or you can change it in the column's settings to use it with one property only. Keep in mind that this change will not convert the underlying YAML to an inline format, it was meant to work with metadata already formatted as inline.
 
 If there is no metadata in your notes, it will be created when you fill the corresponding cell in the database. 
 
 ## Appearance
 
-You can enable text wrapping and you can change the text alignment between `right-aligned`, `centered`, `left-aligned`, and `justified` from the column setting of the **text**, **number**, and **formula** properties.
+You can enable text wrapping and you can change the text alignment between `right-aligned`, `centered`, `left-aligned`, and `justified` from the column settings of the **text**, **number**, and **formula** properties.

docs/docs/features/Viewing data.md

@@ -40,12 +40,12 @@ You can view the database markdown note by using the command `open as markdown`
 
 ## Embedding Database
 
-You can embed a database by using this format `![[database file name.md]]`, it'll show a dataview query of the database.
+You can embed a database in another note by using this format `![[database file name.md]]`, it'll show a dataview query of the database.
 
 ## Exporting Data
 
 You can export the database into **CSV** format using the database menu.
 
 ## Importing Data
 
-You can upload a **CSV** file and turn it to a database using the database menu.
+You can upload a **CSV** file and turn it into a database using the database menu. The **CSV** file has to have a header row and before importing you need to define the column used to create the files in the plugin global settings under `CSV section > mandatory header key`.

docs/docs/index.md

@@ -16,4 +16,4 @@ There are 3 ways of creating a database:
 
 ## How Do I Access Settings?
 
-There are two types of settings (plugin setting and database setting). You can access the database settings from the obsidian menu or from the database menu. The database settings take priority over the plugin settings.
+There are two types of settings (plugin global settings and database settings). You can access the database settings from the obsidian menu or from the database menu. The database settings take priority over the plugin global settings.