Skip to content

Revise Pharos and JSTOR descriptions in README#1336

Merged
daneah merged 2 commits into
ithaka:developfrom
elisa-vargas:patch-1
Jul 16, 2026
Merged

Revise Pharos and JSTOR descriptions in README#1336
daneah merged 2 commits into
ithaka:developfrom
elisa-vargas:patch-1

Conversation

@elisa-vargas

@elisa-vargas elisa-vargas commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Updated the description of Pharos and JSTOR for to align with updated branding guidelines.

This change: (check at least one)

  • Adds a new feature
  • Fixes a bug
  • Improves maintainability
  • Improves documentation
  • Is a release activity

Is this a breaking change? (check one)

  • Yes
  • No

Is the: (complete all)

  • Title of this pull request clear, concise, and indicative of the issue number it addresses, if any?
  • Test suite(s) passing?
  • Code coverage maximal?
  • Changeset added?

What does this change address?

This change updates README text based on feedback and revised copy provided by the Communications team. It addresses the need to align the README language with the latest approved messaging.

How does this change work?

  • Replaces existing README copy with updated text provided by the copy manager
  • Makes no functional or code-level changes
  • Keeps the update limited to documentation/content only

Additional context

This is a text-only documentation update. There are no product, behavior, or implementation changes in this pull request.

Updated the description of Pharos and JSTOR for to align with updated branding guidelines.
@elisa-vargas
elisa-vargas requested a review from a team as a code owner July 16, 2026 22:09
@elisa-vargas
elisa-vargas requested review from jialin-he, lizlove and shoupeva-ithaka and removed request for a team July 16, 2026 22:09
@changeset-bot

changeset-bot Bot commented Jul 16, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0a1cc24

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@daneah
daneah merged commit 2e9847a into ithaka:develop Jul 16, 2026
5 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants