add with keyword

changelog.md

@@ -2,7 +2,7 @@
 
 # 0.2.3
 
-- add `include` statement instead of `import` action
+- add `include file.heta type heta with {}` statement instead of `import` action
 
 # 0.2.2
 

include.md

@@ -5,13 +5,21 @@ It is designed for two objectives:
 - split the whole platform to subfiles for better code management;
 - allow whiting code in various formats.
 
-1. **Heta-file** is not only files containing Heta code but all other files that can be translated to Heta platform: xlsx, sbml, json, etc. 
+1. **Heta-file** means file that can be translated to Heta platform: xlsx, sbml, json, etc. 
 
 1. The identifier of the heta-file is the absolute path of file in file system. For example:  `y:/the-platform/src/index.heta`.
 
-1. The file can be loaded also by `include` action, but it is not recommended. See [actions](./actions#include).
+1. A file can be loaded also by `include` action, but it is not recommended. See [actions](./actions#include).
 
-1. The `include` have `type` property. The default type is `heta` and it means the file includes just regular Heta code.
+1. `include` has `type` property. The default type is `heta` and it means the file includes just regular Heta code.
+
+1. `include` can set additional parameters after `with` keyword in dictionary format
+
+    ```heta
+    include file.xlsx type xlsx with {
+        options: { sheetNum: [1, 2], omitRows: 3 }
+    }
+    ```
 
 1. If you use another file type: `xlsx`, `dbsolve`, this means the code from the files will be parsed and transformed to heta format and can be used as regular Heta code. See [workflow](./workflow).