[docs] Fix vale warning about Latin abbrv., inconsistent case in headings and update verbiage (#24452)Co-authored-by: Bartosz Kaszubowski <[email protected]>
[docs] Fix incorrect platform order and latin abbreviation usage warnings from Vale (#24338)
[docs] minor tweaks and fixes for doc pages (#22587)Co-authored-by: Aman Mittal <[email protected]>
[expo-updates] Support 204 status for no-op responses (#22348)
[docs][expo-updates] Update protocol definition of a multipart body with 0 parts (#22322)
[docs] Move Expo Updates v0 Technical Spec to /archive (#21706)
[exupdates] Move version 1 of the protocol out of draft (#21703)# Why Version 1 of the spec is now implemented in both iOS and Android on the main branch, so the version of the spec can now be
[exupdates] Move version 1 of the protocol out of draft (#21703)# Why Version 1 of the spec is now implemented in both iOS and Android on the main branch, so the version of the spec can now be brought out of draft state and version 0 can be put in the archive. # How Grep. # Test Plan Run the docs site locally, see nav works. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin).
show more ...
[docs] Add redirects based on Sentry reports and fix formatting in tutorial (#21657)
[expo-updates] Update spec for version 1: message part (#20259)
[docs] Fix the "-" character in Expo Update tech specs (#20709)
[docs][expo-updates] Clarify "extra" field in expo-updates protocol (#20293)# Why Part (2) of https://github.com/expo/custom-expo-updates-server/issues/12#issuecomment-1334121928. # How A
[docs][expo-updates] Clarify "extra" field in expo-updates protocol (#20293)# Why Part (2) of https://github.com/expo/custom-expo-updates-server/issues/12#issuecomment-1334121928. # How Add more clarifying language to indicate how other libraries may choose to interact with the expo-updates protocol. # Test Plan Proofread. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg: updated a module plugin). Co-authored-by: Aman Mittal <[email protected]>
[docs] squash several typos, gramma fixes (#19927)Co-authored-by: Aman Mittal <[email protected]>
[docs] update lint setup, run Prettier on MDX (#19323)
Rename from .md to .mdx (#19255)
[docs] fix part of broken links reported by Algolia crawler (#18895)
[expo-updates] Clarify spec for assetRequestHeaders (#18528)
[expo-updates][android] Allow null asset hash in new manifests (#17466)
[docs] Fix typos (#17256)
[expo-updates] Fix asset hash encoding specification (#16170)
[expo-updates] Update spec for asset hash verification (#16109)
[docs] Update default branch to main
[expo-updates] Specify hex encoding for sha-256 asset hash fields (#15555)
[expo-updates] Add codesigning to spec (#14853)
[expo-updates] Fix headers location in expo-updates multipart response spec (#15495)
[docs][expo-updates] Update spec for multipart manifest responses (#15389)
12