more links

docs/db-models.md

@@ -2330,7 +2330,7 @@ Phalcon's resultsets emulate scrollable cursors. You can get any row just by acc
 
     Some database systems do not support scrollable cursors. This forces Phalcon to re-execute the query, in order to rewind the cursor to the beginning and obtain the record at the requested position. Similarly, if a resultset is traversed several times, the query must be executed the same number of times.
 
-Storing large query results in memory will consume many resources. You can however instruct Phalcon to fetch data in chunks of rows, thus reducing the need to re-execute the request in many cases. You can achieve that by setting the `orm.resultset_prefetch_records` setup value. This can be done either in `php.ini` or in the model `setup()`. More information about this can be found in the [features](#disablingenabling-features) section.
+Storing large query results in memory will consume many resources. You can however instruct Phalcon to fetch data in chunks of rows, thus reducing the need to re-execute the request in many cases. You can achieve that by setting the `orm.resultset_prefetch_records` setup value. This can be done either in `php.ini` or in the model `setup()`. More information about this can be found in the [features](#disablingenablingfeatures) section.
 
 Note that resultsets can be serialized and stored in a cache backend. [Phalcon\Cache\Cache][cache] can help with that task. However, serializing data causes [Phalcon\Mvc\Model][mvc-model] to retrieve all the data from the database in an array, thus consuming more memory while this process takes place.
 

docs/filter-filter.md

@@ -573,7 +573,7 @@ $filteredIp = $locator->sanitize('127.0.0.1', 'ipv4');
 [ucwords]: https://www.php.net/manual/en/function.ucwords.php
 [utf8_decode]: https://www.php.net/manual/en/function.utf8-decode.php
 [filter-exception]: api/phalcon_filter.md#filterexception
-[filter-filter]: api/phalcon_filter.md#filter
+[filter-filter]: api/phalcon_filter.md
 [filter-filterfactory]: api/phalcon_filter.md#filterfilterfactory
 [filter-filterinterface]: api/phalcon_filter.md#filterfilterinterface
 [filter-sanitize-absint]: api/phalcon_filter.md#filtersanitizeabsint

docs/translate.md

@@ -369,7 +369,7 @@ $translator = $factory->newInstance('csv', $options);
 
 In the above example, you can see the usage of `delimiter` and `enclosure`. In most cases, you will not need to supply these options but in case your CSV files are somewhat different, you have the option to instruct the adapter as to how it will parse the contents of the translation file.
 
-Creating this adapter can be achieved by using the [Translate Factory][translate-factory], but you can instantiate it directly:
+Creating this adapter can be achieved by using the [Translate Factory][translatefactory], but you can instantiate it directly:
 ```php
 <?php
 
@@ -434,7 +434,7 @@ translations/
             translations.po
 ```
 
-Creating this adapter can be achieved by using the [Translate Factory][translate-factory], but you can instantiate it directly:
+Creating this adapter can be achieved by using the [Translate Factory][translatefactory], but you can instantiate it directly:
 ```php
 <?php
 
@@ -653,4 +653,3 @@ $translator = $factory->newInstance(
 [wiki-gettext]: https://en.wikipedia.org/wiki/Gettext
 [di]: di.md
 [routing]: routing.md
-[translate-factory]: #translatefactory