[DOC]Update documents

[BAOOOOOM]

Thanks for sending a pull request!
Please make sure you click the link above to view the contribution guidelines,
then fill out the blanks below.

Description

(Brief description on what this PR is about)

What does this implement/fix? Explain your changes.

Keep pace with dev.

1.Update AUTHORS.md
2.Update CHANGE.txt
3.Update EduNLP/I2V/init.py
4.Update EduNLP/I2V/i2v.py
5.Update EduNLP/SIF/parser/parser.py
6.Update EduNLP/SIF/segment/segment.py
7.Update EduNLP/SIF/sif.py
8.Update EduNLP/SIF/tokenization/tokenization.py
9.Update EduNLP/Tokenizer/tokenizer.py
10.Update EduNLP/Vector/t2v.py
11.Update examples/i2v/get_pretrained_i2v_d2v_w2v.ipynb
12.Update examples/tokenizer/tokenizier.ipynb
13.Update setup.py
14.Update tests/test_i2v/test_pretrained.py
15.Update tests/test_sif/test_segement.py
16.Update tests/test_vec/test_vec.py

Pull request type

• [DATASET] Add a new dataset
• [BUGFIX] Bugfix
• [FEATURE] New feature (non-breaking change which adds functionality)
• [BREAKING] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [STYLE] Code style update (formatting, renaming)
• [REFACTOR] Refactoring (no functional changes, no api changes)
• [BUILD] Build related changes
• [DOC] Documentation content changes
• [OTHER] Other (please describe):

Changes

1.Update AUTHORS.md
2.Update CHANGE.txt
3.Update EduNLP/I2V/init.py
4.Update EduNLP/I2V/i2v.py
5.Update EduNLP/SIF/parser/parser.py
6.Update EduNLP/SIF/segment/segment.py
7.Update EduNLP/SIF/sif.py
8.Update EduNLP/SIF/tokenization/tokenization.py
9.Update EduNLP/Tokenizer/tokenizer.py
10.Update EduNLP/Vector/t2v.py
11.Update examples/i2v/get_pretrained_i2v_d2v_w2v.ipynb
12.Update examples/tokenizer/tokenizier.ipynb
13.Update setup.py
14.Update tests/test_i2v/test_pretrained.py
15.Update tests/test_sif/test_segement.py
16.Update tests/test_vec/test_vec.py

Does this close any currently open issues?

N/A

Any relevant logs, error output, etc?

N/A

Checklist

Before you submit a pull request, please make sure you have to following:

Essentials

• PR's title starts with a category (e.g. [BUGFIX], [FEATURE], [BREAKING], [DOC], etc)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage and al tests passing
• Code is well-documented (extended the README / documentation, if necessary)
• If this PR is your first one, add your name and github account to AUTHORS.md

Comments

• If this change is a backward incompatible change, why must this change be made.
• Interesting edge cases to note here