Fix anchor links

Author: kylekatarnls

docs/guide/advanced-features/macro.md

@@ -32,8 +32,12 @@ Note that the closure is preceded by `static` and uses `self::this()` (available
 
 By following this pattern you ensure other developers of you team (and future you) can rely safely on the assertion: `Carbon::anyMacro()` is equivalent to `Carbon::now()->anyMacro()`. This makes the usage of macros consistent and predictable and ensures developers that any macro can be called safely either statically or dynamically.
 
+<div id="macro-cli"><!-- Link anchor --></div>
+
 The sad part is IDE will not natively your macro method (no auto-completion for the method `diffFromYear` in the example above). But it's no longer a problem thanks to our CLI tool: [carbon-cli](https://github.com/kylekatarnls/carbon-cli) that allows you to generate IDE helper files for your mixins and macros.
 
+<div id="user-settings"><!-- Link anchor --></div>
+
 Macros are the perfect tool to output dates with some settings or user preferences.
 
 ```php
@@ -206,7 +210,7 @@ Carbon::resetMacros(); // resetMacros remove all macros and generic macro declar
 
 ```
 
-And guess what? all macro methods are also available on [`CarbonInterval`](#api-interval) and [`CarbonPeriod`](#api-period) classes.
+And guess what? all macro methods are also available on [`CarbonInterval`](../specialized-use/carbon-interval.html) and [`CarbonPeriod`](../specialized-use/carbon-period.html) classes.
 
 ```php
 

docs/guide/date-time-manipulation/addition-and-subtraction.md

@@ -110,7 +110,9 @@ echo $dt->subMonths(2);
 
 This will apply for methods `addMonth(s)`, `subMonth(s)`, `add($x, 'month')`, `sub($x, 'month')` and equivalent quarter methods. But it won't apply for intervals objects or strings like `add(CarbonInterval::month())` or `add('1 month')`.
 
-Static helpers exist but are deprecated. If you're sure to need to apply global setting or work with version 1 of Carbon, [check the overflow static helpers section](#overflow-static-helpers)
+Static helpers exist but are deprecated. If you're sure to need to apply global setting or work with version 1 of Carbon, [check the overflow static helpers section](../date-time-manipulation/addition-and-subtraction.html#overflow-static-helpers)
+
+<div id="overflow-static-helpers"><!-- Link anchor --></div>
 
 You can prevent the overflow with `Carbon::useMonthsOverflow(false)`
 

docs/guide/date-time-manipulation/difference-for-humans.md

@@ -62,7 +62,7 @@ echo Carbon::create(2018, 2, 26, 4, 29, 43)->longRelativeDiffForHumans(Carbon::c
 
 ```
 
-You can also change the locale of the string using `$date->locale('fr')` before the diffForHumans() call. See the [localization](#api-localization) section for more detail.
+You can also change the locale of the string using `$date->locale('fr')` before the diffForHumans() call. See the [localization](../getting-started/localization.html) section for more detail.
 
 <div id="diff-for-humans-options"><!-- Link anchor --></div>
 

docs/guide/date-time-manipulation/difference.md

@@ -2,7 +2,7 @@
 
 `Carbon` `diff()` and `diffAsCarbonInterval()` methods return a `CarbonInterval` (since Carbon v3, while it returned `DateInterval` in the previous versions).
 
-Check [CarbonInterval chapter](#api-interval) for more information.
+Check [CarbonInterval chapter](../specialized-use/carbon-interval.html) for more information.
 
 We also provide `diffAsDateInterval()` act like `diff()` but returns a `DateInterval` instance.
 

docs/guide/date-time-manipulation/string-formatting.md

@@ -57,4 +57,4 @@ echo $dt;
 
 ```
 
-Note: For localization support see the [Localization](#api-localization) section.
+Note: For localization support see the [Localization](../getting-started/localization.html) section.

docs/guide/getting-started/instantiation.md

@@ -154,7 +154,7 @@ Note 1: 2018-02-29 also throws an exception while 2020-02-29 does not since 2020
 
 Note 2: `Carbon::createSafe(2014, 3, 30, 1, 30, 0, 'Europe/London')` also produces an exception as this time is in an hour skipped by the daylight saving time.
 
-Note 3: The PHP native API allow to consider there is a year `0` between `-1` and `1` even if it doesn't regarding Gregorian calendar. That's why years lower than 1 will throw an exception using `createSafe`. Check [isValid()](#doc-method-Carbon-isValid) for year-0 detection.
+Note 3: The PHP native API allow to consider there is a year `0` between `-1` and `1` even if it doesn't regarding Gregorian calendar. That's why years lower than 1 will throw an exception using `createSafe`. Check [isValid()](../../develop/reference.html#carbon-isvalid) for year-0 detection.
 
 ```php{no-render}
 Carbon::createFromFormat($format, $time, $tz);
@@ -243,7 +243,10 @@ echo $carbon->toDateTimeString();
 
 ```
 
-Carbon 2 (requiring PHP >= 7.1) perfectly supports microseconds. But if you use Carbon 1 and PHP < 7.1, read our [section about partial microseconds support](#partial-microseconds-support).
+<details>
+<summary>
+Carbon 2 (requiring PHP >= 7.1) perfectly supports microseconds. But if you use Carbon 1 and PHP < 7.1, [click here to read our section about partial microseconds support](#partial-microseconds-support).
+</summary>
 
 ### Partial microseconds support
 Before PHP 7.1 DateTime microseconds are not added to `"now"` instances and cannot be changed afterward, this means:
@@ -279,3 +282,5 @@ var_dump(Carbon::isMicrosecondsFallbackEnabled()); // true
 echo Carbon::now()->micro; // microtime in all PHP version
 
 ```
+
+</details>

docs/guide/getting-started/localization.md

@@ -59,7 +59,7 @@ In the example above, it will try to find translations in "xx" in priority, then
 
 Note that you can also use an other translator with `Carbon::setTranslator($custom)` as long as the given translator implements [`Symfony\Component\Translation\TranslatorInterface`](https://symfony.com/doc/current/translation.html). And you can get the global default translator using `Carbon::getTranslator()` (and `Carbon::setFallbackLocale($custom)` and `Carbon::getFallbackLocale()` for the fallback locale, setFallbackLocale can be called multiple times to get multiple fallback locales) but as those method will change the behavior globally (including third-party libraries you may have in your app), it might cause unexpected results. You should rather customize translation using custom locales as in the example above.
 
-Carbon embed a default translator that extends Symfony\\Component\\Translation\\Translator You can [check here the methods we added to it](#symfony-translator-details).
+Carbon embed a default translator that extends `Symfony\\Component\\Translation\\Translator` You can [check here the methods we added to it](#symfony-translator-details).
 
 You can check what's supported with the following methods:
 
@@ -128,7 +128,7 @@ echo $notificationForJohn;
 
 You can call any static Carbon method on a factory (make, now, yesterday, tomorrow, parse, create, etc.) Factory (and FactoryImmutable that generates CarbonImmutable instances) are the best way to keep things organized and isolated. As often as possible we recommend you to work with UTC dates, then apply locally (or with a factory) the timezone and the language before displaying dates to the user.
 
-What factory actually do is using the method name as static constructor then call `settings()` method which is a way to group in one call settings of locale, timezone, months/year overflow, etc. ([See references for complete list.](#doc-method-Carbon-settings))
+What factory actually do is using the method name as static constructor then call `settings()` method which is a way to group in one call settings of locale, timezone, months/year overflow, etc. ([See references for complete list.](../../develop/reference.html#carbon-settings))
 
 ```php
 $factory = new Factory([
@@ -563,7 +563,7 @@ echo $translator->getMessages('en')['from_now'];
 
 ```
 
-`setMessages` is equivalent to `setTranslations` but you can omit the locale as it will use the current one, so we recommend to use it when you can as in [this previous example](#custom-translations).
+`setMessages` is equivalent to `setTranslations` but you can omit the locale as it will use the current one, so we recommend to use it when you can as in [this previous example](#localization).
 
 ### Supported Locales
 <!--@include: @/parts/localization/supported-locales.md-->

docs/guide/specialized-use/carbon-time-zone.md

@@ -42,7 +42,7 @@ echo $tz->toOffsetName($summer);
 
 The default timezone is given by [date\_default\_timezone\_get](https://www.php.net/manual/en/function.date-default-timezone-get.php) so it will be driven by the INI settings [date.timezone](https://www.php.net/manual/en/datetime.configuration.php#ini.date.timezone) but you really should override it at application level using [date\_default\_timezone\_set](https://www.php.net/manual/en/function.date-default-timezone-set.php) and you should set it to `"UTC"`, if you're temped to or already use an other timezone as default, please read the following article: [Always Use UTC Dates And Times](https://medium.com/@kylekatarnls/always-use-utc-dates-and-times-8a8200ca3164).
 
-It explains why UTC is a reliable standard. And this best-practice is even more important in PHP because the PHP DateTime API has many bugs with offsets changes and DST timezones. Some of them appeared on minor versions and even on patch versions (so you can get different results running the same code on PHP 7.1.7 and 7.1.8 for example) and some bugs are not even fixed yet. So we highly recommend to use UTC everywhere and only change the timezone when you want to display a date. See our [first macro example](#user-settings).
+It explains why UTC is a reliable standard. And this best-practice is even more important in PHP because the PHP DateTime API has many bugs with offsets changes and DST timezones. Some of them appeared on minor versions and even on patch versions (so you can get different results running the same code on PHP 7.1.7 and 7.1.8 for example) and some bugs are not even fixed yet. So we highly recommend to use UTC everywhere and only change the timezone when you want to display a date. See our [first macro example](../advanced-features/macro.html#user-settings).
 
 While, region timezone ("Continent/City") can have DST and so have variable offset during the year, offset timezone have constant fixed offset: