How do you translate frequency, period, hertz, kilohertz, megahertz and gigahertz without changing the timing or signal meaning? Start by separating frequency from the event being counted. Frequency tells us how many cycles or recurring events occur per unit time; period tells us how long one cycle takes. In SI, the hertz, symbol Hz, is equivalent to s⁻¹. A careful translation must preserve the quantity, value, prefix, reference clock, waveform or event definition and any relationship between frequency and period.
This matters in electronics, radio, audio, telecommunications, computing, power systems, vibration, control engineering, sampling, clocks, rotating machinery, spectroscopy and measurement. A fluent translation can still be technically wrong if 50 Hz becomes 50 kHz, if period is translated as frequency, if MHz is confused with megabits per second, if angular frequency in rad/s is labelled hertz, or if a sampling rate is mistaken for the signal frequency being sampled. High-intent searches about translating Hz are therefore questions about preserving cycles, timing and system behavior.
This article is a specialist child of eduKateSG’s established translation architecture. It does not compete with the master translation system or the protected Vocabulary Learning Hub and How English Works ecosystem. It solves one precise problem: how to move frequency and period language across languages while preserving SI units, prefixes, formulas, event definitions, signal relationships and engineering consequences. The BIPM defines the second through a fixed caesium frequency and states that Hz is equal to s⁻¹; that metrological foundation anchors the translation practice below.
1. Frequency counts recurring events per unit time
Frequency describes how often a defined event repeats. The event might be an electrical cycle, a sound-wave oscillation, a vibration, a clock transition or a pulse. Translation must preserve what is being counted, not merely the word frequency. A value of 100 Hz is incomplete without context if several signals exist. Keep the quantity label, event definition and measurement point together so readers know which recurring phenomenon the number belongs to.
2. Hertz means reciprocal seconds
The SI unit hertz, symbol Hz, is equal to s⁻¹. One hertz therefore corresponds to one specified cycle or event per second. Hz is an international symbol, not an abbreviation to translate into target-language initials. Preserve the symbol exactly and translate only the surrounding description. When spelling out hertz in prose, follow target-language grammar without changing the numerical value or the physical definition.
3. Period is the duration of one cycle
Period answers a different question from frequency: how long does one cycle take? For a simple periodic process, frequency and period are reciprocals. A translation that swaps the two can invert the engineering meaning. Preserve symbols such as f and T, unit labels such as Hz and s, and the direction of any formula. If a period is given in milliseconds or microseconds, protect the prefix with the same care as the value.
4. Frequency and period are reciprocal, not synonymous
Higher frequency usually means shorter period for the same periodic phenomenon. That relationship is useful for QA. If a target states that frequency increases while period also increases under the same reciprocal relationship, investigate. Translators should use equations as semantic evidence, especially in short captions and tables where the prose is minimal. Mathematical relationships can catch terminology errors that ordinary spellchecking cannot see.
5. Hz is not cycles per minute
Hertz is based on seconds. Rotational or mechanical documentation may instead use revolutions per minute, strokes per minute or cycles per minute. Do not label those values Hz without conversion. A translation can preserve rpm or another source unit while explaining it in the target language. If conversion is required, separate the mathematical step from the language step and control rounding.
6. kHz changes scale by one thousand
One kilohertz equals one thousand hertz. Losing the k prefix changes a value by three orders of magnitude. Treat 44.1 kHz or 100 kHz as one protected measurement string. This is especially important in audio, radio and sampling documentation where Hz and kHz can appear on adjacent lines. The target must preserve prefix case, decimal punctuation and the relationship between the value and its signal.
7. MHz changes scale by one million
One megahertz equals one million hertz. MHz is common in radio, clocks, processors and instrumentation. Uppercase M matters: it is the SI prefix mega. Do not let a style transformation or OCR pipeline lowercase the prefix. When a target language uses a translated word for megahertz, the symbol MHz still stays unchanged in numerical data.
8. GHz changes scale by one billion
One gigahertz equals one billion hertz. The scale matters in microwave, wireless and computing contexts. A 2.4 GHz carrier is not 2.4 MHz, and a 3.2 GHz processor clock is not a data-transfer rate of 3.2 gigabits per second. Keep the quantity name near the unit so readers do not mistake frequency for bandwidth, bit rate or another performance measure.
9. Frequency is not data rate
Hz measures cycles or events per second; bit/s measures information transfer. A communication system can use a carrier frequency in MHz or GHz while carrying data at a different number of megabits per second. Translating MHz as megabits per second is a category error. Preserve frequency units, data-rate units and the labels that tell readers which quantity the specification describes.
10. Frequency is not bandwidth
Bandwidth is a span or range of frequencies, not necessarily the same as a signal’s center or carrier frequency. Both can use Hz, kHz, MHz or GHz, so the unit alone does not distinguish them. Preserve terms such as center frequency, lower cutoff, upper cutoff and bandwidth. In translated RF and filter specifications, check that every frequency value remains attached to the same role.
11. Carrier frequency is not modulation frequency
A modulated signal can contain a high-frequency carrier and lower-frequency modulation components. If a target uses one generic frequency term for both, readers can misinterpret system behavior. Keep carrier, modulation, symbol, tone and clock qualifiers where the source uses them. Technical translation often depends on preserving relationships among several frequencies rather than translating one isolated number.
12. Sampling rate is not automatically signal frequency
A digital system can sample a signal at 48 kHz even though the audio frequencies of interest are much lower. Sampling rate describes how often measurements are taken, not the frequency of the waveform being measured. Preserve sample rate, signal frequency and clock rate as separate quantities. In software and audio documentation, these words may appear close together and share the same unit family.
13. Clock frequency describes repeated timing events
A processor or digital circuit clock provides recurring timing events, commonly expressed in MHz or GHz. Clock frequency should not be translated as computation speed in every context; performance also depends on architecture and workload. Preserve the technical quantity and let the target sentence explain its role. Avoid marketing-style paraphrases that turn a measured frequency into a broader performance claim.
14. Pulse repetition frequency needs its own label
Radar, lasers and pulsed systems can specify pulse repetition frequency, meaning how often pulses repeat. That is different from the carrier frequency inside each pulse. Translating both simply as frequency can collapse two independent scales. Preserve the full term or established acronym and verify which waveform the value belongs to. Timing diagrams are strong evidence when prose is ambiguous.
15. Line frequency and mains frequency are power-system terms
Power systems commonly operate around a specified mains or line frequency such as 50 Hz or 60 Hz. The translation should preserve nominal frequency, allowable tolerance and any measured deviation. Do not convert the value merely because another country uses a different grid standard. A translated equipment specification should describe the source requirement, not silently adapt it to the reader’s local electricity system.
16. Audio frequency and sample rate must stay distinct
Audio documentation can contain audible-band frequencies, filter cutoffs, tone frequencies and sample rates on the same page. Preserve the noun attached to each Hz value. A 1 kHz test tone and a 48 kHz sample rate are not two ways of describing the same signal. In translation, keep tone, sample, cutoff and bandwidth labels explicit so the numerical relationships remain intelligible.
17. Resonant frequency belongs to a system response
Mechanical, electrical and acoustic systems can have resonant frequencies where response is strongly affected by stored energy and damping. Do not translate resonance as ordinary repetition rate. Preserve whether the source says natural frequency, resonant frequency or forced excitation frequency. Several may coexist, and the same unit does not make them interchangeable.
18. Natural frequency is not always measured resonance
A model can predict natural frequency while a test identifies a resonant peak under real damping and boundary conditions. A translated report should preserve the distinction between calculated, measured and identified values. If the source includes mode numbers, direction or boundary conditions, keep them attached to the same frequency.
19. Vibration frequency can coexist with rotational speed
A rotating machine can run at a shaft speed expressed in rpm while vibration spectra are shown in Hz. Harmonics may appear at one times, two times or other multiples of running speed. Do not relabel rpm as Hz without conversion. Keep rotational-speed and vibration-frequency quantities distinct so diagnostic meaning survives.
20. Angular frequency uses rad/s rather than Hz
Angular frequency is commonly written ω and measured in radians per second. Frequency f in hertz and angular frequency are related by 2π, but they are not numerically identical. The site already has a separate angular-velocity owner; this article stays with ordinary frequency and period while making the boundary clear. Translation should preserve f, ω, Hz and rad/s exactly.
21. Frequency is not angular velocity
Angular velocity describes rotational change in angle per unit time, while frequency counts recurring cycles. A rotating object may have both a rotational frequency and an angular velocity related mathematically. Do not use one target term for both simply because each concerns repeated motion. Preserve the quantity symbol and unit as anchors.
22. Wavelength is related to frequency through propagation speed
For waves, wavelength and frequency are connected through the propagation speed. Translating one does not permit changing the other independently. In radio, optics or acoustics, preserve whether the source gives free-space wavelength, wavelength in a medium or another effective value. Units alone do not state the medium.
23. Filter cutoff frequency has a defined role
A filter specification may list lower cutoff, upper cutoff, center frequency and bandwidth. Each can use the same unit. Translate the role labels with care and keep every number attached to the correct response feature. Graphs are especially useful for checking whether the target terminology matches the plotted transfer function.
24. Center frequency is not the same as bandwidth
A band can be centered at one frequency while spanning a much smaller or larger frequency width. If a table loses the words center or bandwidth, the same MHz unit can conceal a serious semantic error. Preserve the pair as separate fields in text, tables and software interfaces.
25. Lower and upper frequency limits must remain ordered
Specifications commonly state a frequency range from a lower limit to an upper limit. Decimal punctuation, column order or right-to-left layout can accidentally reverse the endpoints. QA should parse both values numerically and confirm low remains below high after localization.
26. Frequency tolerance is not frequency itself
Oscillators and clocks may specify nominal frequency together with tolerance in ppm, percent or an absolute frequency unit. Keep nominal value, tolerance and stability metrics separate. A target that folds tolerance into the main number can overstate accuracy or change the acceptance criterion.
27. Frequency stability is a time-dependent specification
Stability can describe how frequency varies over time, temperature or other conditions. Translate the condition and averaging interval, not only the word stability. A clock can have excellent nominal accuracy but different short-term or long-term stability, so one generic target term may not be enough.
28. Phase and frequency are related but distinct
Phase describes position within a cycle; frequency describes how quickly cycles repeat. A translated controls or signal-processing document should not replace phase shift with frequency shift or vice versa. Preserve degrees or radians separately from Hz and check diagrams where the relationship is visually encoded.
29. Frequency drift is not the same as offset
Frequency offset can describe a difference from a reference at a given time, while drift describes change over time. A target that uses one word for both can misstate oscillator behavior. Preserve reference value, sign and observation interval.
30. Doppler shift changes observed frequency
Motion can shift observed frequency relative to a source or reference. Translation should preserve whether the source refers to emitted, received, shifted or center frequency. Direction matters because approach and recession produce opposite shifts under the usual convention.
31. Frequency response describes behavior across frequency
A frequency response is not one frequency. It describes how gain, phase or another response changes across a range. Translation should preserve whether a graph is amplitude response, phase response or a combined transfer-function view. The x-axis may use logarithmic frequency while the y-axis uses decibels or another quantity.
32. Harmonics are integer-related frequencies
Harmonics occur at integer multiples of a fundamental frequency. The word harmonic should not be translated as merely pleasant or musical in technical contexts. Keep fundamental, second harmonic, third harmonic and harmonic order distinct. In power-quality, audio and vibration work, the same terminology can carry safety or diagnostic consequences.
33. Subharmonics and interharmonics need precise labels
Not every spectral component is a harmonic. Subharmonics and interharmonics follow different relationships to the fundamental. Preserve those prefixes and the frequency values that support them. A general word for secondary frequency can erase the mathematical relationship the engineer needs.
34. Fundamental frequency depends on context
The fundamental may be the lowest frequency in a periodic waveform, the primary structural mode or the nominal power-system frequency depending on context. Translate the surrounding domain term rather than treating fundamental as a universal synonym for base. Equations and spectra help identify the intended sense.
35. Spectral peaks need labels as well as numbers
A spectrum can contain many peaks. Translating only the frequency axis without preserving peak annotations, source labels or channel names can make diagnostics impossible. Keep each frequency attached to the same component, order, sensor or signal path.
36. Frequency bins are analysis intervals
Digital spectral analysis divides a frequency range into bins determined by the sampling and transform setup. Bin frequency is not automatically an actual physical tone. Preserve FFT size, resolution and bin terminology when translating signal-analysis documentation.
37. Frequency resolution is not instrument accuracy
Resolution describes the spacing or ability to distinguish nearby frequencies; accuracy describes closeness to the true or reference value. Translating both as precision hides an important measurement distinction. Preserve the numeric basis and test condition.
38. Nyquist frequency is tied to sample rate
For uniformly sampled data, the Nyquist frequency is half the sampling rate. A translation that confuses those two values can misstate anti-aliasing requirements. Keep sampling rate, Nyquist frequency and signal bandwidth separately labelled.
39. Aliasing creates false apparent frequencies
When a signal is inadequately sampled, higher-frequency content can appear as lower-frequency components. Translate alias, aliasing and anti-alias filter with established signal-processing terminology rather than ordinary-language equivalents. The phenomenon is about representation, not a second real source frequency.
40. Beat frequency is a difference frequency
Two close frequencies can produce a beat at their difference. Preserve which frequencies are original and which is the beat. In audio, sensing and heterodyne systems, translating every component simply as tone can obscure the relationship.
41. Heterodyne and intermediate frequency require system context
Receivers and measurement systems can mix signals to produce an intermediate frequency. Carrier, local oscillator and intermediate frequency can all use MHz. Preserve the signal path labels and mixer relationship; the unit alone cannot tell the reader which one is which.
42. Frequency deviation is not carrier frequency
Frequency-modulated systems can specify a carrier plus a deviation around that carrier. Translating deviation as frequency without the relational word can inflate or misstate the actual operating range. Keep sign, peak or RMS convention and modulation context.
43. Channel spacing is a frequency interval
Wireless systems may specify channels by center frequency and spacing. Channel spacing is a difference between adjacent channels, not the channel’s own frequency. Preserve both fields and any guard-band terminology.
44. Oscillator startup and lock frequency are different ideas
Control loops and synthesizers can specify capture, lock, hold or startup ranges around a nominal frequency. These terms describe system behavior, not just another frequency label. Translate them using the control or RF context and keep range endpoints attached to the correct condition.
45. Frequency counters measure under a timebase
A frequency counter derives results from a reference timebase and gate interval. A translated instrument manual should keep gate time, resolution, reference oscillator and input frequency separate. Otherwise users can mistake a configuration parameter for the measured signal.
46. Decimal separators can change apparent frequency magnitude
A frequency such as 2.400 MHz can be misread under different decimal and grouping conventions. Localize numbers only under a controlled rule and test parsed values, not just typography. Radio and timing specifications are especially vulnerable because a punctuation change can move a value by orders of magnitude.
47. Prefix case is part of the unit
kHz, MHz and GHz use standardized prefixes. Automatic capitalization or lowercasing can damage those symbols. Protect the complete measurement token and compare source and target case sensitively. Do not let a title-style function rewrite unit symbols.
48. Period prefixes need equal care
Period may be expressed in milliseconds, microseconds, nanoseconds or picoseconds. ms, µs, ns and ps differ by large scale factors. Preserve the prefix and decimal value together. If the micro sign cannot be represented reliably in a system, use a project-approved alternative rather than improvising.
49. Superscripts in s⁻¹ need robust encoding
Hertz can be represented dimensionally as reciprocal seconds. Plain-text conversions can lose the superscript minus sign and produce ambiguous notation. Keep mathematical typography intact or use an unambiguous project-approved ASCII form. Do not turn s⁻¹ into s because that reverses the dimension.
50. Tables need header-level frequency control
A single header may define Hz or MHz for hundreds of values. If the header is mistranslated or the prefix changes, every row becomes wrong. Audit table titles, units, channel labels, ranges and footnotes before checking individual numbers.
51. Graph axes are part of the measurement
Spectra, Bode plots and frequency-response graphs encode meaning through axis scales, logarithmic spacing, units and legends. Translating only captions is insufficient. Verify that axes, tick labels, reference lines and annotations remain consistent with the underlying data.
52. OCR often confuses Hz prefixes
Scanned manuals can turn kHz into Hz, MHz into mHz or misread decimal punctuation. Always compare OCR-derived frequency values with the source image before translation. A plausible-looking frequency can still be wrong by a factor of a thousand or a million.
53. Machine translation should lock frequency measurements
Language models do not need to alter numerical values or unit symbols to translate the surrounding prose. Mask frequency and period strings, then restore and validate them. This prevents unsolicited conversion, prefix changes and accidental substitution from nearby sentences.
54. Translation memory should treat values as variables
Repeated instructions can differ only by a frequency value. High fuzzy matches can carry an old number into a new target. Protect measurements as variables and run a source–target diff on all numbers and units before release.
55. Search intent: how to translate Hz
Hz itself does not change language. Translate the quantity and event definition around it: signal frequency, mains frequency, tone, clock, vibration or another recurring event. Keep the symbol and value unchanged unless an explicit conversion is requested.
56. Search intent: how to translate kHz, MHz and GHz
The prefixes do not become target-language initials. kHz, MHz and GHz remain standardized symbols. The important translation work is identifying what the number describes and protecting scale.
57. Search intent: frequency versus period
When users ask the difference, the simplest reliable distinction is that frequency counts cycles per second while period measures time per cycle. Preserve f and T, Hz and seconds, and verify the reciprocal relationship when both values appear.
58. BIPM SI guidance anchors the unit system
The BIPM defines the second through the caesium frequency and states that the hertz is equal to s⁻¹. Use BIPM guidance on the second and the SI Brochure when formal metrology matters. These references help separate standardized unit meaning from local editorial preference.
59. Connect upward to the master translation architecture
This page owns frequency and period translation, not general localization. Broader technical-translation systems, terminology governance and QA belong to eduKateSG’s existing master translation architecture. Keeping the boundary clear prevents a specialist owner from competing with canonical broad hubs.
60. Connect sideways to Vocabulary Learning and How English Works
Frequency work depends on precise distinctions among rate, cycle, period, carrier, sampling, bandwidth, harmonic, phase, drift and tolerance. The protected Vocabulary Learning Hub and How English Works ecosystem support the language layer while this page protects timing and measurement meaning.
Release checklist
Before publication, compare every frequency and period value; verify Hz, kHz, MHz and GHz prefixes; distinguish signal frequency from sample rate, clock rate, data rate and bandwidth; keep angular frequency separate from ordinary frequency; review decimal formatting, graphs and table headers; and preserve the event definition behind every number.
Final rule: translate the event, preserve the timing
Frequency tells us how often something repeats; period tells us how long one cycle lasts. A successful translation keeps the same event, the same value, the same unit, the same scale and the same mathematical relationships. When those survive, the target language can change without changing the system’s timing.
61. Frequency measurement needs a defined observation interval
Frequency estimates can depend on gate time, averaging time or analysis-window length. A translated instrument procedure should preserve those timing conditions. A number without the measurement interval can appear more precise than it really is, especially for unstable or slowly varying signals.
62. Instantaneous frequency is a specialized signal concept
In time-varying signals, instantaneous frequency describes local phase evolution rather than a single constant repetition rate. Do not translate it as simply current frequency without preserving the signal-processing sense. Context from phase, modulation or analytic-signal formulas should guide terminology.
63. Average frequency can hide variation
An average over time can match a nominal value even when the signal fluctuates significantly. Preserve whether the source reports mean, instantaneous, peak deviation or Allan-type stability measures. The averaging definition is part of the result, not an optional explanatory detail.
64. Repetition rate can describe non-sinusoidal events
Not every Hz value belongs to a sine wave. Lasers, packet generators, pulse trains and mechanical cycles can all have repetition rates. Translate the event being repeated and avoid adding waveform assumptions that the source does not make.
65. Frame rate is not always expressed or interpreted as hertz
Video and display systems may use frames per second alongside refresh frequency in hertz. The values can be related but are not necessarily identical. Preserve frame rate, refresh rate and scan timing as separate specifications.
66. Refresh rate belongs to the display system
A display refresh rate describes how often the screen updates, not the frequency content of the image itself. Do not translate a 120 Hz display specification as a signal bandwidth or frame rate unless the source explicitly makes that relation.
67. Symbol rate is not carrier frequency
Digital communications may specify symbol rate in baud and carrier frequency in Hz. They describe different parts of the system. A translator should preserve baud, bit/s and Hz as separate unit families and keep modulation context explicit.
68. Baud and bit rate are not automatically equal
One symbol can encode more than one bit depending on modulation. Translating baud as bits per second can therefore change system capacity. Preserve the quantity name and unit rather than replacing both with a general word for speed.
69. Frequency sweep parameters form a relationship
A sweep can specify start frequency, stop frequency, step size, dwell time and sweep rate. Translating each field independently without preserving the relationship can create impossible settings. QA should reconstruct the sweep from the target values.
70. Sweep rate is frequency change per unit time
Sweep rate can use units such as Hz/s or MHz/s. It is not a frequency itself. Preserve the denominator and the concept of change over time. Losing “per second” turns a rate into a static frequency.
71. Frequency calibration uses traceable references
Calibration reports can compare an applied reference frequency with an indicated or generated value. Translate reference, indication, error, correction and uncertainty separately. A correct Hz value in the wrong column can still invalidate the result.
72. Frequency accuracy can be stated in ppm
Oscillator accuracy may be specified in parts per million rather than hertz. Preserve whether ppm applies to nominal frequency, temperature drift or aging. Do not silently convert relative specifications into absolute Hz without declaring the reference value.
73. Aging changes oscillator frequency over time
Oscillator aging is a time-dependent drift specification. Translate the interval, rate and sign convention precisely. “Per year,” “per day” and cumulative limits are not interchangeable even when all refer to the same oscillator.
74. Temperature coefficient links frequency to temperature
Frequency can vary with temperature. A specification may state a coefficient, a total stability band or a compensated range. Keep temperature interval, units and frequency reference tied together instead of reducing everything to a general stability statement.
75. Jitter is timing variation, not frequency itself
Clock jitter describes short-term timing variation and may be expressed in seconds, unit intervals or phase-related measures. It is related to frequency performance but is not simply another frequency value. Preserve the measurement domain and statistical definition.
76. Phase noise is reported around a carrier
Phase-noise plots use offset frequency from a carrier and a noise-density quantity on the vertical axis. Translating the offset as carrier frequency can make the graph meaningless. Keep carrier, offset and noise units distinct.
77. Frequency uncertainty belongs to the measured result
A measured frequency can include an uncertainty statement with coverage or confidence information. Do not translate uncertainty as tolerance or specification limit. Preserve the metrological relationship between result and uncertainty.
78. Software labels may hide the unit in metadata
A UI may show only a number while an API or configuration schema stores Hz, kHz or another unit separately. Localization testing should cover exported data and machine metadata as well as visible labels so the displayed translation cannot detach from the underlying unit.
79. Frequency conversions need explicit rounding
Converting 2.45 GHz to MHz is exact in scale, but displayed decimal places still matter. Define whether the target keeps equivalent precision, adds trailing zeros or follows source formatting. Avoid creating false precision through automatic conversion.
80. The same hertz can describe different domains
Hz can describe mains power, sound, vibration, radio, clocks or repeated events. The unit is stable across languages, but the domain meaning comes from the quantity label and context. Translation succeeds when both the universal unit and the specific phenomenon remain intact.
81. Frequency limits can be regulatory as well as technical
Radio and communications systems can operate only within assigned bands, emission masks or channel plans. Translate regulatory labels and region-specific conditions carefully. A familiar MHz value does not imply permission to use the same frequency in every jurisdiction.
82. Nominal frequency is not exact measured frequency
A system described as 50 Hz or 60 Hz can vary around its nominal value. Preserve nominal, measured, commanded and calibrated distinctions. The target should not imply perfect constancy when the source gives tolerance or control limits.
83. Frequency setpoint and measured frequency are different fields
Generators, drives and test equipment can show a target setpoint alongside actual measured output. Translate command, setpoint, output and measurement separately. A valid Hz value in the wrong field can mislead troubleshooting.
84. Variable-frequency drives use output frequency as a control variable
Motor drives vary electrical frequency to control machine operation. Output frequency, motor speed and commanded speed are related but not identical. Preserve whether a parameter belongs to the supply, drive output or mechanical shaft.
85. Frequency converters can change one mains frequency to another
Equipment may convert between supply frequencies or generate a programmable output. Translation should preserve input frequency, output frequency, range and nominal values. Do not localize a 60 Hz requirement into 50 Hz simply because the reader lives in a 50 Hz country.
86. Resonance warnings can be safety-critical
Rotating equipment and structures may prohibit continuous operation near resonant frequencies. Translate avoidance bands, dwell limits and speed relationships conservatively. A missing range boundary can turn a warning into an unsafe instruction.
87. Frequency-dependent specifications need the test frequency
Impedance, capacitance, noise and many sensor characteristics vary with frequency. If a value is measured at 1 kHz, that condition belongs to the specification. Preserve test frequency with the reported result instead of treating it as a disposable footnote.
88. Time-domain and frequency-domain views describe the same signal differently
A waveform can be described by period in the time domain and spectral components in the frequency domain. Translation should preserve which representation is being discussed. Terms such as spectrum, waveform, period and harmonic are not interchangeable.
89. Frequency-domain averages need their method
Spectral analyzers can average power, magnitude or complex data using different methods. Translating all averaging as simple arithmetic mean can be misleading. Keep averaging type, window and bandwidth information when they affect the result.
90. Final QA should reconstruct the timing relationships
Before release, choose representative values and verify period, frequency, sample rate, bandwidth, speed and angular-frequency relationships mathematically. This catches errors that lexical QA misses. If the target numbers no longer tell a physically consistent timing story, the translation is not finished.