adjust wording regarding offsets

the article linked in the ranking criteria doesn't describe what is
meant by "offset", which in this case is timing point offset and one
instance of video offset. offset-related articles will be reworked as
per ppy#7254

wiki/Beatmapping/Timing/en.md

@@ -1,6 +1,6 @@
 # Timing
 
-**Timing** is the process of determining a song's musical structure by finding its [BPM](/wiki/Beatmapping/Beats_per_minute), one or more [offsets](/wiki/Disambiguation/Offset) (timing points) for each [timing section](/wiki/Beatmapping/Timing_section), and its [time signatures](/wiki/Music_theory/Time_signature).
+**Timing** is the process of determining a song's musical structure by determining the positions of each [timing section](/wiki/Beatmapping/Timing_section) along with their [BPM](/wiki/Beatmapping/Beats_per_minute) values and [time signatures](/wiki/Music_theory/Time_signature).
 
 The [beatmap editor](/wiki/Client/Beatmap_editor) provides [timing settings](/wiki/Client/Beatmap_editor/Timing) with a [ruler-like timeline view](/wiki/Client/Beatmap_editor/Timelines#timing) for temporal placement of [hit objects](/wiki/Gameplay/Hit_object). When objects are placed, they are [snapped](/wiki/Beatmapping/Snapping) to timeline ticks, i.e. subdivisions of a [measure](/wiki/Music_theory/Measure), allowing objects to easily line up with notes of the song.
 
@@ -32,7 +32,7 @@ Almost every song can be divided into sections of different tempo, and the goal
 
 ### Single BPM
 
-A beatmap's first [offset](/wiki/Beatmapping/Offset) ([uninherited timing point](/wiki/Client/Beatmap_editor/Timing#uninherited-timing-point), i.e. "red line") is the amount of time between the beginning of the audio file and the first downbeat, and the starting point used by osu! to calculate positions of other beats. A single timing point is often enough for songs that are digitally produced or edited seamlessly, having no BPM or time signature changes, or metronome resets<!-- TODO: link -->.
+The amount of time between the beginning of the audio file and the first downbeat, also called "offset", is typically the place for the first [uninherited timing point](/wiki/Client/Beatmap_editor/Timing#uninherited-timing-point), the starting point used by osu! to calculate positions of other beats. One of these timing points is often enough for songs that are digitally produced or edited seamlessly, having no BPM or time signature changes, or metronome resets<!-- TODO: link -->.
 
 In the [timing tab](/wiki/Client/Beatmap_editor/Timing), tapping the `T` key or clicking the metronome button to the beat of the song will allow osu! to calculate an approximate BPM. The value can then be adjusted manually until it is correct and all timeline ticks line up with the music. There are a few things to note:
 
@@ -49,6 +49,8 @@ Music that is performed without a metronome may often contain timing discrepanci
 
 For single- or multi-BPM songs performed with a metronome, small timing errors (e.g. a note played a few milliseconds early or late) may be ignored if the beatmap is still playable with simple timing. Alternatively, the audio file may be edited directly with a program like [Audacity](https://www.audacityteam.org/) to quantise notes and correct timing mistakes.
 
+Some songs require timing points that shift offset without changing BPM or time signature. These are usually caused by inaccurate quantisation or added/removed beats from a single measure.
+
 Lastly, a new timing point is required for time signature changes and metronome resets. For example, a regular rhythm may change to a waltz, making the measure not 4, but 3 beats long, or a new measure may start earlier than expected, which necessitates a new timing point to reset the metronome.
 
 ## Community reception

wiki/Disambiguation/Offset/en.md

@@ -4,13 +4,14 @@
 
 ## Timing settings
 
-- An [uninherited ("red") offset](/wiki/Beatmapping/Offset), which denotes either the song's first downbeat, or the start of a new timing section
-- [Online offset](/wiki/Beatmap/Online_offset), a timing change applied by [NAT](/wiki/People/The_Team/Nomination_Assessment_Team) to ranked beatmaps with incorrect uninherited offset in order to adjust it
-- [Local ("offline") offset](/wiki/Glossary/Local_song_offset), a per-beatmap setting that shifts the objects in time during gameplay
-- [Universal offset](/wiki/Client/Options/Universal_offset), the osu! client setting that globally affects the timing of beatmaps
+- An [uninherited timing point](/wiki/Client/Beatmap_editor/Timing#uninherited-timing-point) ("red line"), the start of a new [timing section](/wiki/Beatmapping/Timing_section). Timing points reside at an offset relative to the start of the audio file, but the timing point itself is also sometimes called "offset".
+- A beatmap "offset", the amount of time between the start of the audio file and the song's first [downbeat](/wiki/Music_theory/Downbeat) measured in milliseconds.
+- [Online offset](/wiki/Beatmap/Online_offset), a timing change applied by [NAT](/wiki/People/The_Team/Nomination_Assessment_Team) to ranked beatmaps with incorrect beatmap offset in order to adjust it.
+- [Local ("offline") offset](/wiki/Glossary/Local_song_offset), a per-beatmap setting that shifts the objects in time during gameplay.
+- [Universal offset](/wiki/Client/Options/Universal_offset), the osu! client setting that globally affects the timing of beatmaps.
 
 ## Beatmap settings
 
-- Countdown offset, a setting which affects the appearance of [countdown](/wiki/Beatmapping/Countdown) before the first hit object
-- Audio offset, or [audio lead-in](/wiki/Glossary/Lead-in)
-- Video offset, a setting that shows how soon a background video should play relatively to the audio track
+- Countdown offset, a setting which affects the appearance of [countdown](/wiki/Beatmapping/Countdown) before the first hit object.
+- Audio offset, or [audio lead-in](/wiki/Beatmap/Lead-in).
+- Video offset, a setting that shows how soon a background video should play relatively to the audio track.

wiki/Ranking_Criteria/en.md

@@ -176,8 +176,8 @@ This category contains explicit allowance statements of concepts and rules that
 ### Rules
 
 - **[Uninherited timing points](/wiki/Client/Beatmap_editor/Timing#uninherited-timing-point) must be used to accurately beatmap the song's time signatures.** If an incorrect time signature lasts for more than one bar, an uninherited timing point must be added on the next downbeat to reset the time signature. For #/4-signatures unsupported by the editor, metronome resets or editing of the `.osu` file are acceptable. For other unsupported time signatures, refer to this [exemplary chart](/wiki/shared/timing/Timing_signature_reference_chart.png), and see the [Timing songs with #/8-signatures](/wiki/Guides/Timing_Songs_With_8-Signatures) guide for further information.
-- **Beatmaps must be perfectly timed.** This means [BPM](/wiki/Beatmapping/Beats_per_minute) and [offset](/wiki/Beatmapping/Offset) are exactly synchronised with the song. Beatmaps with constantly changing BPM may be impossible to perfectly time and should instead be as accurate as possible without negatively affecting gameplay. Complex timing during breaks or spinners is optional.
-- **[Uninherited timing points](/wiki/Client/Beatmap_editor/Timing#uninherited-timing-point) must be the same in every difficulty of a beatmap.** Each point must have the same [BPM](/wiki/Beatmapping/Beats_per_minute) and [offset](/wiki/Beatmapping/Offset) in each difficulty.
+- **Beatmaps must be perfectly timed.** This means [BPM](/wiki/Beatmapping/Beats_per_minute) and offset of each [uninherited timing point](/wiki/Client/Beatmap_editor/Timing#uninherited-timing-point) are exactly synchronised with the song. Beatmaps with constantly changing BPM may be impossible to perfectly time and should instead be as accurate as possible without negatively affecting gameplay. Complex timing during breaks or spinners is optional.
+- **[Uninherited timing points](/wiki/Client/Beatmap_editor/Timing#uninherited-timing-point) must be the same in every difficulty of a beatmap.** Each point must have the same [BPM](/wiki/Beatmapping/Beats_per_minute) and offset in each difficulty.
 - **[Uninherited timing points](/wiki/Client/Beatmap_editor/Timing#uninherited-timing-point) should only be used when required for timing purposes.** Unnecessary timing points may unintentionally affect main-menu pulsing, add unwanted sounds to the [Nightcore mod](/wiki/Gameplay/Game_modifier/Nightcore), or cause timing to shift. Acceptable uses include:
   - Aligning beats of the Nightcore mod with the start of musical sections.
   - Accommodating for objects in musical sections requiring unsupported beat snap divisors (e.g. 1/11).
@@ -235,7 +235,7 @@ This category contains explicit allowance statements of concepts and rules that
   - **Maximum file size:** 2.5MB
 - **A video's dimensions must not exceed a width of 1280 and a height of 720 pixels.** Additionally, upscaling lower resolution video to a higher resolution should be avoided. This ensures video files do not become excessively large or resource intensive.
 - **A video must be encoded in H.264.**
-- **A video's [offset](/wiki/Beatmapping/Offset) must be correct if it synchronizes with the song.** An incorrect offset can result in a misleading visual representation of the song. If the same video appears in multiple difficulties, it must always have the same offset(s).
+- **A video's offset must be correct if it synchronizes with the song.** An incorrect offset can result in a misleading visual representation of the song. If the same video appears in multiple difficulties, it must always have the same offset(s).
 - **A video's audio track must be removed from the video file.** The audio track in a video is not used in osu!, and removing it reduces the file size of the beatmap. This includes videos with muted audio tracks.
   - *See [Compressing files § Video](/wiki/Guides/Compressing_files#video) for guidance.*