Update README.md

README.md

@@ -14,21 +14,21 @@
 
 ### With Cleaner.jl you will be able to:
 
-- Format column names to make them unique and fit snake_case or camelCase style.
+- Format column names to make them unique and fit `snake_case` or `camelCase` style.
 - Remove rows and columns with different kinds of empty values.
 e.g: `missing`, `""`, `"NA"`, `"None"`
 - Delete columns filled with just a constant value.
 - Use a row as the names of the columns.
 - Minimize the amount of element types for each column without making the column of type `Any`.
 - Automatically use multiple threads if your data is big enough (and you are running `Julia` with more than 1 thread).
-- Rematerialize your original source [Tables.jl](https://github.com/JuliaData/Tables.jl) type, as CleanTable implements the [Tables.jl](https://github.com/JuliaData/Tables.jl) interface too.
+- Rematerialize your original source [Tables.jl](https://github.com/JuliaData/Tables.jl) type, as `CleanTable` implements the [Tables.jl](https://github.com/JuliaData/Tables.jl) interface too.
 
 ### To keep in mind
 
-All non mutating functions (those ending without a `!`) recieve a table as argument and return a `CleanTable`.
-All mutating functions (those ending with a `!`) recieve a CleanTable and return a `CleanTable`.
+All non mutating functions (those ending without a `!`) recieve a `table` as argument and return a `CleanTable`.
+All mutating functions (those ending with a `!`) recieve a `CleanTable` and return a `CleanTable`.
 
-So you can start your workflow with a non mutating function and continue using mutating ones.
+So you can start your workflow with a non mutating function and continue it using mutating ones if you prefer.
 E.g.
 
 ```julia