OliveGrove
Pressing the Word of God for Deeper Understanding.

Bible text policy

Translation and Text Notes

OliveGrove reads from the Berean Standard Bible by default and keeps the World English Bible available as a public-domain alternate. The reader, focused Bible ranges, study workspace, Language tab, Discourse tab, and Bible reference links all use the same translation-aware contract.

Why BSB Is The Default

The Berean Standard Bible gives OliveGrove a public-domain English Bible text with a connected original-language study layer. The BSB word table supplies verse-level headings, cross references, translator footnotes, Strong's links, transliteration, and parsing data that can be surfaced without mixing Bible text and commentary.

Berean states that the Berean Bible and Majority Bible texts were dedicated to the public domain on April 30, 2023. See the official Berean terms and Berean downloads.

Why WEB Remains Available

The World English Bible remains useful as a public-domain comparison text. Keeping WEB available lets readers compare wording, inspect alternate phrasing, and use the parallel reader without leaving the site.

The translation toggle changes the displayed Scripture text. OliveGrove study notes, lexical comments, discourse comments, and theological summaries remain separate governed content.

Textual Differences

Some verse numbers differ between English Bible traditions. When BSB does not include a verse number that WEB includes, OliveGrove treats that as a source-text fact rather than a broken route. Focused ranges still render the available verses and show a notice for omitted verse numbers.

Examples include familiar textual-note locations such as Acts 8:37, John 5:4, several verses in Matthew and Mark, Acts 28:29, and Romans 16:24. These are handled as translation and textual tradition matters, not as hidden editorial changes.

Original-Language Data

BSB+ data is presented as a study aid. A word-study panel may show a BSB phrase, source-language form when available, Strong's code, transliteration, parsing, and a lexicon link. These fields help readers inspect how a translation is connected to Hebrew, Aramaic, or Greek data.

OliveGrove does not treat a Strong's link or parsing label as a complete interpretation. Lexical meaning, syntax, discourse flow, and theology still require context and governed study notes.

Reference Layers

The chapter reader can show more than one kind of reference. BSB references come from the BSB source artifacts. Classic cross-references come from OpenBible.info's verse-level cross-reference data, a Treasury-derived corpus used here as reference links rather than quoted Bible text. OliveGrove study links come from governed passage companion data.

These layers are study helps, not alternate Scripture texts. They help readers see related passages while keeping translation data, public-domain reference data, and OliveGrove explanations visibly distinct.

Source Boundaries

  • Bible text comes from the selected public-domain translation.
  • BSB headings, footnotes, cross references, Strong's links, transliteration, and parsing come from BSB source artifacts.
  • Classic cross-reference links are normalized from the OpenBible.info cross-reference dataset and do not include quoted Scripture text.
  • OliveGrove comments, summaries, discourse notes, lexicon notes, and theological links are separate curated artifacts.
  • Reference links use canonical Bible routes. Translation preference stays reader state, not a different URL.