This is the first entry in Word Matters, a series on language, Scripture, and confidence for ordinary Christians.
Two frustrations often sit side by side in people’s minds. First: “Why can’t the Bible just say what it means?!” And second: “Do I really need Greek or Hebrew to make sense of anything?” Add to that the feeling that some preachers weaponise the original languages, and it’s no wonder thoughtful Christians feel torn.
I’m not a linguist, and I’m not pretending to be one. But I’ve spent years working with Scripture, thinking about how words carry meaning, and watching how small details can open Scripture rather than close it. The original languages really do help, but you don’t need to be fluent to read your Bible well. In fact, relying on English translations is normal and expected — and God has used those translations to grow the church for centuries.
It’s also true that you can get sound theology even from imperfect translations. That’s because good translations are usually “imperfect” in harmless ways, and because Scripture’s big, central truths don’t hang on obscure footnotes. And on the rare occasions where translation choices do matter, a little explanation can go a long way.
So why Word Matters? Because words carry worlds. They shape how we hear God speak. And they remind us that Scripture came to us in real languages, through real people, in real history — not as a hazy spiritual mist.
In the next entry, I’ll share how this all began for me: a conversation in the Singles Quarters at JCH that opened my eyes to how words — even small ones — can make the Bible feel both more human and more divine at the same time.
Word Matters aims to give ordinary Christians confidence in the words God has preserved for us — and to enjoy the rich, sometimes surprising history behind them.