From f9cf5d0d420d196576dfd97810bc1e2241f0bc1d Mon Sep 17 00:00:00 2001 From: Tom Keffer Date: Sat, 22 Jul 2023 13:59:59 -0700 Subject: [PATCH] Follow canonical form for anchors --- docs_src/custom/cheetah-generator.md | 6 +++--- docs_src/custom/custom-reports.md | 2 +- docs_src/custom/database.md | 15 +++++++-------- docs_src/custom/introduction.md | 2 +- docs_src/hardware/fousb.md | 2 +- docs_src/reference/weewx-options/stations.md | 2 +- 6 files changed, 14 insertions(+), 15 deletions(-) diff --git a/docs_src/custom/cheetah-generator.md b/docs_src/custom/cheetah-generator.md index 1dc1e9f7..30a45ffb 100644 --- a/docs_src/custom/cheetah-generator.md +++ b/docs_src/custom/cheetah-generator.md @@ -360,7 +360,7 @@ Where: _`period`_ is the _aggregation period_ over which the aggregation is to be done. Possible choices are listed in the -[aggregation periods table](#aggregation_periods). +[aggregation periods table](#aggregation-periods). _`data_binding`_ is a _binding name_ to a database. An example would be `wx_binding`. See the section @@ -399,7 +399,7 @@ value will appear. See the section _[Formatting options](#formatting-options)_. There are several _aggregation periods_ that can be used: - +
@@ -1055,7 +1055,7 @@ pressure. Here are some examples: Note how you can explicitly specify a time interval in the tag itself (2nd row in the table above). If you do not specify a value, then a default time interval, set by option -[time_delta](../../reference/skin-options/units/#time_delta) in the skin +[`time_delta`](../../reference/skin-options/units/#time_delta) in the skin configuration file, will be used. This value can be retrieved by using the syntax `$trend.time_delta` (4th row in the table). diff --git a/docs_src/custom/custom-reports.md b/docs_src/custom/custom-reports.md index 2c9eecd1..c469d4cc 100644 --- a/docs_src/custom/custom-reports.md +++ b/docs_src/custom/custom-reports.md @@ -357,7 +357,7 @@ For example, this would result in a date/time string such as Each _unit system_ is a set of units. For example, the `METRIC` unit system uses centimeters for rain, kilometers per hour for wind speed, and degree Celsius for temperature. The option -[unit_system](../../reference/weewx-options/stdreport/#unit_system) +[`unit_system`](../../reference/weewx-options/stdreport/#unit_system) controls which unit system will be used in your reports. The available choices are `US`, `METRIC`, or `METRICWX`. The option is case-insensitive. See [_Units_](../../reference/units) for the units defined in each of these unit diff --git a/docs_src/custom/database.md b/docs_src/custom/database.md index 254497d2..be0141a6 100644 --- a/docs_src/custom/database.md +++ b/docs_src/custom/database.md @@ -340,14 +340,13 @@ copying it to a new database, performing the unit conversion along the way. You then use this new database. The general strategy is identical to the strategy outlined above in the section -[*Reconfigure database using new -schema*](#reconfigure_database_using_new_schema). The only difference is that -instead of specifying a new starting schema, you specify a different database -unit system. This means that instead of steps 1 and 2 above, you edit the -configuration file and change option `target_unit` in section -[`[StdConvert]`](../../reference/weewx-options/stdconvert) to -reflect your choice. For example, if you are switching to metric units, the -option will look like: +[*Reconfigure database using new schema*](#reconfigure-using-new-schema). The +only difference is that instead of specifying a new starting schema, you specify +a different database unit system. This means that instead of steps 1 and 2 +above, you edit the configuration file and change option `target_unit` in +section [`[StdConvert]`](../../reference/weewx-options/stdconvert) to reflect +your choice. For example, if you are switching to metric units, the option will +look like: ``` ini [StdConvert] diff --git a/docs_src/custom/introduction.md b/docs_src/custom/introduction.md index fdf00d40..81b2902b 100644 --- a/docs_src/custom/introduction.md +++ b/docs_src/custom/introduction.md @@ -542,7 +542,7 @@ the type, such as the minimum and maximum value seen during the day, and at what time. These tables have names such as `archive_day_outTemp` or `archive_day_barometer`. They are there to optimize certain types of queries — their existence is generally transparent to the user. For more details, -see the section [_Daily summaries_](../../devnotes#Daily_summaries) in the +see the section [_Daily summaries_](../../devnotes#daily-summaries) in the _Developer's Notes_. ### Binding names diff --git a/docs_src/hardware/fousb.md b/docs_src/hardware/fousb.md index bf801e44..2b732806 100644 --- a/docs_src/hardware/fousb.md +++ b/docs_src/hardware/fousb.md @@ -15,7 +15,7 @@ save up to 3264 historical readings. When WeeWX starts up it will attempt to download all records from the console since the last record in the archive database. -## Polling mode and interval {id=polling_mode_and_the_polling_interval} +## Polling mode and interval When reading 'live' data, WeeWX can read as fast as possible, or at a user-defined period. This is controlled by the option `polling_mode` in the diff --git a/docs_src/reference/weewx-options/stations.md b/docs_src/reference/weewx-options/stations.md index e248dab4..e1b5ecc9 100644 --- a/docs_src/reference/weewx-options/stations.md +++ b/docs_src/reference/weewx-options/stations.md @@ -263,7 +263,7 @@ One of `PERIODIC` or `ADAPTIVE`. In `PERIODIC` mode, WeeWX queries the console at regular intervals determined by the polling_interval. In `ADAPTIVE` mode, WeeWX attempts to query the console at times when it is not reading data from the sensors or writing data to memory. See the section [*Polling mode and -interval*](../../../hardware/fousb/#polling_mode_and_the_polling_interval) +interval*](../../../hardware/fousb/#polling-mode-and-interval) in the *Hardware Guide* for more details. The default is `PERIODIC`.
Aggregation periods