Update ATF importer

README.md

@@ -494,8 +494,8 @@ poetry run python -m ebl.atf_importer.application.atf_importer -i "ebl/atf_impor
 
 #### Troubleshooting
 
-If a fragment cannot be imported check the console output for errors. Also check the specified log folder (`error_lines.txt`,`unparseable_lines_[fragment_file].txt`, `not_imported.txt`) and see which lines could not be parsed.
-If lines are faulty, fix them manually and retry the import process. If tokes are not lemmatized correctly, check the log-file `not_lemmatized.txt`.
+If a fragment cannot be imported check the console output for errors. Also check the specified log folder (`error_lines.txt`,`unparsable_lines_[fragment_file].txt`, `not_imported_files.txt`) and see which lines could not be parsed.
+If lines are faulty, fix them manually and retry the import process. If tokes are not lemmatized correctly, check the log-file `not_lemmatized_tokens.txt`.
 
 ## Acknowledgements
 

docs/ebl-atf.md

@@ -8,7 +8,7 @@ encoding. The grammar definitions below use [EBNF](https://en.wikipedia.org/wiki
 The EBNF grammar below is an idealized representation of the eBL-ATF as it does
 not deal with ambiguities and implementation details necessary to create the
 domain model in practice. A fully functional grammar is defined in
-[ebl-atf.lark](https://github.com/ElectronicBabylonianLiterature/ebl-api/blob/master/ebl/transliteration/domain/ebl_atf.lark).
+[ebl-atf.lark](https://github.com/ElectronicBabylonianLiterature/ebl-api/blob/master/ebl/transliteration/domain/atf_parsers/lark_parser/ebl_atf.lark).
 The file uses the EBNF variant of the [Lark parsing library](https://github.com/lark-parser/lark).
 See [Grammar Reference](https://lark-parser.readthedocs.io/en/latest/grammar/)
 and [Lark Cheat Sheet](https://lark-parser.readthedocs.io/en/latest/lark_cheatsheet.pdf).