README.md in lokalise_manager-3.0.0 vs README.md in lokalise_manager-3.1.0

@@ -109,20 +109,20 @@
 
 * `import_opts` (`hash`) — options that will be passed to Lokalise API when downloading translations to your app. Here are the default options:
 
 ```ruby
 {
-  format: 'yaml',
+  format: 'ruby_yaml',
   placeholder_format: :icu,
   yaml_include_root: true,
   original_filenames: true,
   directory_prefix: '',
   indentation: '2sp'
 }
 ```
 
-Full list of available import options [can be found in the official API documentation](https://app.lokalise.com/api2docs/curl/#transition-download-files-post).
+Full list of available import options [can be found in the official API documentation](https://developers.lokalise.com/reference/download-files).
 
 You can provide additional options, and they will be merged with the default ones. For example:
 
 ```ruby
 importer = LokaliseManager.importer api_token: '1234abc',
@@ -133,19 +133,19 @@
 In this case the `import_opts` will have `original_filenames` set to `true` and will also contain all the defaults (`format`, `placeholder_format`, and others). Of course, you can override defaults as well:
 
 ```ruby
 importer = LokaliseManager.importer api_token: '1234abc',
                                     project_id: '123.abc',
-                                    import_opts: {indentation: '4sp}
+                                    import_opts: {indentation: '4sp'}
 ```
 
 * `import_safe_mode` (`boolean`) — default to `false`. When this option is enabled, the import task will check whether the directory set with `locales_path` is empty or not. If it is not empty, you will be prompted to continue.
 * `max_retries_import` (`integer`) — this option is introduced to properly handle Lokalise API rate limiting. If the HTTP status code 429 (too many requests) has been received, this gem will apply an exponential backoff mechanism with a very simple formula: `2 ** retries`. If the maximum number of retries has been reached, a `RubyLokaliseApi::Error::TooManyRequests` exception will be raised and the operation will be halted.
 
 ### Export config
 
-* `export_opts` (`hash`) — options that will be passed to Lokalise API when uploading translations. Full list of available export options [can be found in the official documentation](https://app.lokalise.com/api2docs/curl/#transition-upload-a-file-post). By default, the following options are provided:
+* `export_opts` (`hash`) — options that will be passed to Lokalise API when uploading translations. Full list of available export options [can be found in the official documentation](https://developers.lokalise.com/reference/upload-a-file). By default, the following options are provided:
   + `data` (`string`, required) — base64-encoded contents of the translation file.
   + `filename` (`string`, required) — translation file name. If the file is stored under a subdirectory (for example, `nested/en.yml` inside the `locales/` directory), the whole path acts as a name. Later when importing files with such names, they will be placed into the proper subdirectories.
   + `lang_iso` (`string`, required) — language ISO code which is determined using the root key inside your YAML file. For example, in this case the `lang_iso` is `en_US`:
 
 ```yaml
@@ -300,6 +300,6 @@
 1. Copypaste `.env.example` file as `.env`. Put your Lokalise API token and project ID inside. The `.env` file is excluded from version control so your data is safe. All in all, we use pre-recorded VCR cassettes, so the actual API requests won’t be sent. However, providing at least some values is required.
 2. Run `rspec .`. Observe test results and code coverage.
 
 ## License
 
-Copyright (c) [Lokalise team](http://lokalise.com), [Ilya Bodrov](http://bodrovis.tech). License type is [MIT](https://github.com/bodrovis/lokalise_manager/blob/master/LICENSE).
+Copyright (c) [Lokalise team](http://lokalise.com), [Ilya Krukowski](http://bodrovis.tech). License type is [MIT](https://github.com/bodrovis/lokalise_manager/blob/master/LICENSE).