English language help required


Recommended Posts

I'm trying to write an english sentence better way. Here is the sentence:

He died at his residence on 10-Feb-2011 naturally.

Is this a correct english ?

what I tried to mean is that the person had a natural death on that date.how do I write a better english here ? can you please correct it ? what are other possibilities here in wrting ?

Need help.

Link to comment
https://www.neowin.net/forum/topic/1153162-english-language-help-required/
Share on other sites

Here is so far I have written this paragraph...I am not sure if this can be written in a better way.

I have known Mr.X at address Flat-2,City-Y,Dist-Z,Pin-K for the last 6 yrs with good physical & mental health to my knowledge. He passed away on the 10th of February, in 2011, of natural causes.

Can I write at address ? Is it correct ?

I am not sure....can you please correct it

It doesn't look too bad. You could just change the word "naturally" to "of natural causes", so that it reads, "He died at his residence on 10-Feb-2011 of natural causes.". Using just the word "naturally" I don't believe is technically improper, but the term used most commonly nowadays when referring to a natural death is "of natural causes".

  • Like 1

This is how I would write it, though it may be different depending on your location as well as your reason for the writing (letter, article, essay):

He passed away from natural causes at his residence on February 10, 2011.

For professional or formal writing, avoid abbreviations such as Feb or yrs. I'd say there's technically nothing wrong with the way you wrote it; it's merely a matter of convention which is something you learn with time.

I have known Mr. X, whom resided at the address Flat-2, City-Y, Dist-Z, Pin-K, for for the last six years and has always appeared in good physical and mental health.

You should always have a space after punctuation, including in "Mr. X" and the comma-separated list. As well, the bit, "to my knowledge," is implied from the context so I feel it's unnecessary.

Edited by Xinok
  • Like 1

This is how I would write it, though it may be different depending on your location as well as your reason for the writing (letter, article, essay):

He passed away from natural causes at his residence on February 10, 2011.

For professional or formal writing, avoid abbreviations such as Feb or yrs. I'd say there's technically nothing wrong with the way you wrote it; it's merely a matter of convention which is something you learn with time.

I have known Mr. X, whom resided at the address Flat-2, City-Y, Dist-Z, Pin-K, for for the last six years and has always appeared in good physical and mental health.

You should always have a space after punctuation, including in "Mr. X" and the comma-separated list. As well, the bit, "to my knowledge," is implied from the context so I feel it's unnecessary.

Thanks Mr Xinok,

I guess you had a typo here ..

I have known Mr. X, whom resided at ....

should have been ....

I have known Mr. X, who resided at ....

is not it ?

Can you please confirm ?

Out of curiosity, why state the address? This is not relevant unless you are writing a legal report or other documentation which requires such data.

This might help with your who vs whom question:

http://www.prdaily.com/Main/Articles/Who_vs_whom_A_simple_trick_for_determining_when_to_8964.aspx

:rolleyes: This is a pathetic euphemism, not correct English.

It is accepted and is correct English, except it is better to say that he died.

  • Like 1

Nope, "whom" would be correct I believe. I can never get it right, myself, but here is the rule

Who is correct, not whom. Who relates to he/she and whom relates to them. If you were to rewrite the sentence accordingly you would say:

have known Mr. X. He resided at ....

Either way, the original sentence is a bit awkward.

It is accepted and is correct English, except it is better to say that he died.

Agreed. Sorry, I didn't mean that "passed away" isn't correct English. I meant that it's not more correct than "died" and shouldn't automatically be used as a replacement in the way that Dushmany suggested.

Told you I could never get it right. :laugh:

:) It is difficult and I think that's why whom is falling out of favour and is rarely used these days.

Who is correct, not whom. Who relates to he/she and whom relates to them. If you were to rewrite the sentence accordingly you would say:

have known Mr. X. He resided at ....

I was trying too hard. :p I know whom to be the objective form of who but haven't quite figured out what that means yet. While I write well, I don't have a good understanding of what makes one form correct or what makes one form better than another. In the end, I simply write whatever sounds good to me.

Ok, how would you have said it, using just the information I had before the OP added to it?

Probably the way Marshall said it right before you posted:

He died in 2011, on the 10th of February of natural causes.

No offence but I can't stand it when people replace died with "passed away". It's an unnecessary Americanism that's creeping into the language for no good reason other than to sugar-coat an unpleasant but normal part of life. It's also a particularly meaningless euphemism given that you don't go anywhere (and certainly don't pass anything) when you die.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!