Corrected documentation to be more gramatically correct

[willsawyerrrr]

Summary

The documentation for useColorScheme() suggested that the user's preferred color scheme will be 'Dark Mode'. Instead suggesting 'Dark Mode' as an example of what the user's preferred color scheme could be is more correct.

Changelog

[INTERNAL] [FIXED] - Edited documentation for useColorScheme() hook
Edited

/**
 * A new useColorScheme hook is provided as the preferred way of accessing
 * the user's preferred color scheme (aka Dark Mode).
 */
export function useColorScheme(): ColorSchemeName;

to

/**
 * A new useColorScheme hook is provided as the preferred way of accessing
 * the user's preferred color scheme (e.g. Dark Mode).
 */
export function useColorScheme(): ColorSchemeName;

Test Plan

Documentation only - no testing required.

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	7,736,137	+732,787
android	hermes	armeabi-v7a	7,140,252	+760,557
android	hermes	x86	8,045,348	+629,162
android	hermes	x86_64	8,015,701	+735,608
android	jsc	arm64-v8a	9,596,918	+728,572
android	jsc	armeabi-v7a	8,363,229	+756,577
android	jsc	x86	9,541,151	+614,919
android	jsc	x86_64	10,133,547	+724,074

Base commit: 87c356d
Branch: main

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
ios	-	universal	n/a	--

Base commit: 87c356d
Branch: main

[facebook-github-bot]

@rshest has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[cipolleschi]

/rebase

[facebook-github-bot]

@rshest has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[react-native-bot]

This pull request was successfully merged by @willsawyerrrr in 74cb441.

^{When will my fix make it into a release? | Upcoming Releases}

[Pranav-yadav]

Hey @cipolleschi @rshest !
Was going through recent PRs.. If I'm correct this PR wasted 1h 38m 43s + 4m 57s of compute time and resources just for testing a DOC/Non Code change.
Which is completely/partly useless¹ as, 1.5h are wasted on testing builds, etc.

I would suggest following things in order to stop the wastage of compute resources for NON CODE/DOC changes:

• Create new label or a command (for fb-github-bot) which in turn triggers the DOC related tests.

  • like only trigger Spell-check and Formatting or Styles related tests.
  • Labels/Commands E.g. doc-change or /no-code or skip-ci

• Encourage collaborators as well as contributors to use following tags/strings in their commit messages to Skip CI or tests from triggering auto.;

  • [skip ci]
  • [ci skip]
  • [no ci]
  • [skip actions]
  • [actions skip]

• Obviously we can enforce Spell-Check and(or) Formatting tests irrespective of the Code/Non Code changes :)

• 🤗🌏 #SaveEarth

Cc: @sammy-SC @hramos

PS: Sorry for tagging all of you, just wanted to make sure this is not ignored
@willsawyerrrr sorry to ping you, but you can also use this in your upcoming PRs not only in this repo but others as well :)