-
WORD Research this...2 Chronicles 11
- 1 And Rehoboam came to Jerusalem, and got together the men of Judah and Benjamin, a hundred and eighty thousand of his best fighting-men, to make war against Israel and get the kingdom back for Rehoboam.
- 2 But the word of the Lord came to Shemaiah, the man of God, saying,
- 3 Say to Rehoboam, the son of Solomon, king of Judah, and to all Israel in Judah and Benjamin,
- 4 The Lord has said, You are not to go to war against your brothers: let every man go back to his house, for this thing is my purpose. So they gave ear to the words of the Lord and were turned back from fighting against Jeroboam.
- 5 Now Rehoboam kept in Jerusalem, building walled towns in Judah.
- 6 He was the builder of Beth-lehem and Etam and Tekoa
- 7 And Beth-zur and Soco and Adullam
- 8 And Gath and Mareshah and Ziph
- 9 And Adoraim and Lachish and Azekah
- 10 And Zorah and Aijalon and Hebron, walled towns in Judah and Benjamin.
- 11 And he made the walled towns strong, and he put captains in them and stores of food, oil, and wine.
- 12 And in every town he put stores of body-covers and spears, and made them very strong. And Judah and Benjamin were his.
- 13 And the priests and Levites who were in all Israel came together to him from every part of their country.
- 14 For the Levites gave up their living-places and their property, and came to Judah and Jerusalem; for Jeroboam and his sons had sent them away, not letting them be priests to the Lord;
- 15 And he himself made priests for the high places, and for the images of he-goats and oxen which he had made.
- 16 And after them, from all the tribes of Israel, all those whose hearts were fixed and true to the Lord, the God of Israel, came to Jerusalem to make offerings to the Lord, the God of their fathers.
- 17 So they went on increasing the power of the kingdom of Judah, and made Rehoboam, the son of Solomon, strong for three years; and for three years they went in the ways of David and Solomon.
- 18 And Rehoboam took as his wife Mahalath, the daughter of Jerimoth, the son of David and of Abihail, the daughter of Eliab, the son of Jesse;
- 19 And she had sons by him, Jeush, Shemariah, and Zaham.
- 20 And after her he took Maacah, the daughter of Absalom; and she had Abijah and Attai and Ziza and Shelomith by him.
- 21 Maacah, the daughter of Absalom, was dearer to Rehoboam than all his wives and his servant-wives: (for he had eighteen wives and sixty servant-wives, and was the father of twenty-eight sons and sixty daughters.)
- 22 Rehoboam made Abijah, the son of Maacah, chief and ruler among his brothers, for it was his purpose to make him king.
- 23 And in his wisdom he had his sons stationed in every walled town through all the lands of Judah and Benjamin; and he gave them a great store of food, and took wives for them.
-
-
King James Version (kjv)
- Afrikaans
- Arabic
- Armenian
- Basque
- Breton
- Chamorro
- Cherokee
- Chinese
- Coptic
- Croatian
- Czech
- Danish
- Dutch
-
English
American King James Version (akjv) American Standard Version (asv) Basic English Bible (basicenglish) Douay Rheims (douayrheims) John Wycliffe Bible (c.1395) (wycliffe) King James Version (kjv) King James Version (1769) with Strongs Numbers and Morphology and CatchWords, including Apocrypha (without glosses) (kjva) Webster's Bible (wb) Weymouth NT (weymouth) William Tyndale Bible (1525/1530) (tyndale) World English Bible (web) Young's Literal Translation (ylt)
- Esperanto
- Estonian
- Finnish
- French
- German
- Gothic
- Greek
- Greek Modern
- Hebrew
- Hungarian
- Italian
- Japanese
- Korean
- Latin
- Latvian
- Lithuanian
- Malayalam
- Manx Gaelic
- Maori
- Myanmar Burmse
- Norwegian bokmal
- Portuguese
- Potawatomi
- Romanian
- Russian
- Scottish Gaelic
- Slavonic Elizabeth
- Spanish
- Swahili
- Swedish
- Syriac
- Tagalog
- Thai
- Turkish
- Ukrainian
- Uma
- Vietnamese
-
-
Active Persistent Session:
To use a different persistent session key, simply add it above, and click the button below.
How This All Works
Your persistent session key, together with your favourite verse, authenticates you. It links to all your notes and tags in the Bible. You can share it with loved ones so they can see your notes and tags.
However, to modify your notes and tags, you need both the persistent session key and your favourite verse.
Please Keep Your Favourite Verse Private
Your persistent session key and favourite verse provide you exclusive access to edit your notes and tags. Think of your persistent session key as a username and your favourite verse as a password. Therefore, ensure your favourite verse is kept private.
The persistent session key allows viewing, while editing is only possible when the correct favourite verse is provided.
-
Loading...
-
-
Basic English Bible (basicenglish - 1.3)
2008-04-21English (en)
1949/1964 Bible in Basic English
Public Domain -- Copy Freely
The Bible In Basic English was printed in 1965 by Cambridge Press in England. Published without any copyright notice and distributed in America, this work fell immediatly and irretrievably into the Public Domain in the United States according to the UCC convention of that time. A call to Cambridge prior to placing this work in etext resulted in an admission of this fact.
For more information about the text, see the file BBE.DOC which contains the printed introduction page.
The most current and correct copies of these files can be obtained from the following. If any errors are located, please ensure you have the latest files, and if so, we would appreciate being informed of the error.
The Bible Foundation
http://www.bf.org
Or by contacting:
Mark Fuller
1129 East Loyola Drive
Tempe, Arizona, 85282
602-829-8542 (voice)- Direction: LTR
- LCSH: Bible. English.
- Distribution Abbreviation: basicenglish
License
Public Domain
Source (OSIS)
Unbound Bible
- history_1.3
- switched to Unbound Bible source and OSIS encoding
- history_1.2
- compressed module
- history_1.1
- minor correction to Rev 12:1
Basic Hash Usage Explained
At getBible, we've established a robust system to keep our API synchronized with the Crosswire project's modules. Let me explain how this integration works in simple terms.
We source our Bible text directly from the Crosswire modules. To monitor any updates, we generate "hash values" for each chapter, book, and translation. These hash values serve as unique identifiers that change only when the underlying content changes, thereby ensuring a tight integration between getBible and the Crosswire modules.
Every month, an automated process runs for approximately three hours. During this window, we fetch the latest Bible text from the Crosswire modules. Subsequently, we compare the new hash values and the text with the previous ones. Any detected changes trigger updates to both our official getBible hash repository and the Bible API for all affected translations. This system has been operating seamlessly for several years.
Once the updates are complete, any application utilizing our Bible API should monitor the hash values at the chapter, book, or translation level. Spotting a change in these values indicates that they should update their respective systems.
Hash values can change due to various reasons, including textual corrections like adding omitted verses, rectifying spelling errors, or addressing any discrepancies flagged by the publishers maintaining the modules at Crosswire.
The Crosswire initiative, also known as the SWORD Project, is the "source of truth" for getBible. Any modifications in the Crosswire modules get reflected in our API within days, ensuring our users access the most precise and current Bible text. We pledge to uphold this standard as long as getBible exists and our build scripts remain operational.
We're united in our mission to preserve the integrity and authenticity of the Bible text. If you have questions or require additional information, please use our support system. We're here to assist and will respond promptly.
Thank you for your understanding and for being an integral part of the getBible community.
Favourite Verse
You should select one of your favourite verses.
This verse in combination with your session key will be used to authenticate you in the future.
This is currently the active session key.
Should you have another session key from a previous session.
You can add it here to load your previous session.