Minor grammar, spelling and correctness fixes in MatchContainer comments.
@@ -37,10 +37,10 @@ const {useMemo} = React;
* ```
* // Media.react.js
*
- * // Define a React component that uses <MatchContainer> to render the
+ * // Define a React component that uses <MatchContainer /> to render the
* // results of a @module selection
* function Media(props) {
- * const {media, ...restPropsj} = props;
+ * const {media, ...restProps} = props;
*
* const loader = moduleReference => {
* // given the data returned by your server for the @module directive,
@@ -48,7 +48,11 @@ const {useMemo} = React;
* // it is loading asynchronously).
* todo_returnModuleOrThrowPromise(moduleReference);
* };
- * return <MatchContainer match={media.mediaAttachment} props={restProps} />;
+ * return <MatchContainer
+ * loader={loader}
+ * match={media.mediaAttachment}
+ * props={restProps}
+ * />;
* }
*
* module.exports = createSuspenseFragmentContainer(
@@ -112,7 +116,7 @@ function MatchContainer<TProps: {...}, TFallback: React.Node | null>({
}
// NOTE: the MatchPointer type has a $fragmentRefs field to ensure that only
// an object that contains a FragmentSpread can be passed. If the fragment
- // spread matches, then the metadata fields below (__id, __fragments, etc)
+ // spread matches, then the metadata fields below (__id, __fragments, etc.)
// will be present. But they can be missing if all the fragment spreads use
// @module and none of the types matched. The cast here is necessary because
// fragment Flow types don't describe metadata fields, only the actual schema
