Skip to content

🎥 Make videos programmatically with React

Remove why both timing docs section

JonnyBurgera1ebf39a571a
diff --git a/packages/docs/docs/sequence.mdx b/packages/docs/docs/sequence.mdx
index f49d0f0b19..ab4a90d110 100644
--- a/packages/docs/docs/sequence.mdx
+++ b/packages/docs/docs/sequence.mdx
@@ -241,8 +241,6 @@ export const MyVideo = () => {
In the example above, `Child` receives frames `15` through `44` and the sequence is visible from composition frame `30` through `59`.
-See [Timing and trimming](/docs/timing#why-both-trimafter-and-durationinframes) for how `trimAfter` and `durationInFrames` differ.
-
### `loop?`
Repeats the child range selected by [`trimBefore`](#trimbefore) and [`trimAfter`](#trimafter). Default: `false`.
diff --git a/packages/docs/docs/timing.mdx b/packages/docs/docs/timing.mdx
index 045f559891..c81bced868 100644
--- a/packages/docs/docs/timing.mdx
+++ b/packages/docs/docs/timing.mdx
@@ -156,15 +156,6 @@ All other items require `trimAfter` to loop, because they have no intrinsic end.
[`<Loop>`](/docs/loop) is a shorthand for the same behavior with a period measured in the parent timeline: `<Loop durationInFrames={50} times={3}>` is equivalent to `trimAfter={50}`, `durationInFrames={150}` and `loop`.
-## Why both `trimAfter` and `durationInFrames`?
-
-`trimAfter` is a position in the child clock, `durationInFrames` is a length in the parent timeline.
-
-They only coincide if `trimBefore` is `0`, `playbackRate` is `1` and the item does not loop.
-
-`loop` needs both: the trim range defines one cycle, `durationInFrames` defines how long the item stays.
-A range of 60 child frames repeated over 90 parent frames cannot be expressed with one prop.
-
## Order of operations
Think of the timing props as applying to the content in this order: