General English (AEC)

1. Technical and Scientific Writing

Technical writing explains a process, a mechanism, or a set of facts so that a reader can use them — repair a cooler, follow a library rule, or operate an instrument. Its reader is a student, a technician, or an office; write for that reader's next action, not for admiration.

Features (Meenakshi Raman's checklist):

• Clear purpose — stated at the start ("How to borrow a book from the reading room").
• Precise words — one term, one meaning. Numbers and units stay exact: 80 seats, 100°C, 5 ml.
• Impersonal voice — passive voice, or a calm we. No slang, no jokes, no metaphors that could be read two ways.
• Headings or numbered steps — the eye finds the next step in a second.
• Definitions where a term is new ("accession number = the library's serial number for a book").

Scientific writing is technical writing tied to observation and test. A short classroom note of an experiment uses a fixed order: Aim → Materials/Apparatus → Method (numbered, past or imperative) → Observation → Result → Conclusion. Claims the test did not make are left out. "The water boiled at 100°C in this lab" is scientific; "the water danced in the beaker" is not.

Two common exam tasks:

• Process: how to do something, in the order the hands move. Use imperative or present simple.
• Mechanism/object: the parts of a thing and what each part does (a cooler, a catalogue, an identity card). Use present simple for a lasting method ("The librarian issues a day-pass") and past simple for one completed test ("The cooler leaked last month").

2. Content Writing and Blogs

Content writing is useful prose for a public page — a college website, a notice-board article, a magazine column, a short feature. Before the first sentence, name two things: the reader and the purpose.

Structure of a content piece:

• Headline that states the topic ("Quiet Hours in the Reading Room").
• Short paragraphs — two to four sentences each; one paragraph does one job.
• Optional sub-headings for longer pieces.
• Facts the reader can check — numbers, names and days in full form a stranger can use ("eight in the morning to six in the evening," not "the usual time").
• A close with a next step — a contact or an action ("The librarian issues a day-pass at the desk").

The voice is plainer than a story and warmer than a lab note. Slang and private jokes stay out. Content writing is not a shopping list of adjectives, and it is not a technical report with Aim and Apparatus — it is public information in readable blocks.

Blog (web log) is a dated public journal on a website — personal but organised. Its parts: a title, a date, a first-person or friendly voice, short screen-sized paragraphs, one thread of thought, and a close that may invite a comment. You may use I. You may end with a question to the reader.

Content writing vs blog: content writing serves a page of information; a blog lets a person be seen beside the information. A blog that only lists moods without a topic is a diary left unlocked — choose a topic a reader can share (the first week of a semester, a bus to college in the rain).

One line on SEO basics: put the topic's key words in the title and first paragraph so search engines (and readers) find the page.

3. Email Writing

An email is a letter sent electronically. It keeps the skeleton of a formal letter, with a subject line added. One email, one main request.

Full format:

• To: receiver's address.
• Subject: names the job in a few words — never blank, never only "Hello" (e.g. "Leave for two days, 22–23 September — BA Sem II").
• Salutation: formal — Dear Sir/Madam (name unknown) or Dear Dr Sharma (name known). Informal — Hi Meena.
• Body: purpose in the first sentence, then the needed facts (dates, roll number, paper name — in full), then a clear request or thanks. Short paragraphs, not one block.
• Complimentary close: Yours faithfully goes with Dear Sir/Madam; Yours sincerely goes with a named salutation like Dear Dr Sharma. Informal: Thanks.
• Signature: your name and class/office.

Tone: polite even in a complaint — state what happened, when, and what you ask the office to do. Do not write your whole life-story in a leave mail. Do not use ALL CAPITALS.

Formal vs informal -- the same facts, different dress:

• Formal (to Principal/HOD/office): full sentences, no contractions ("I shall" not "I'll"), polite request forms ("May I...", "I request...", "Kindly..."), complete details.
• Informal (to a classmate): shorter, friendly, contractions fine ("I'll return it tomorrow"), but still clear -- the request must not get lost in chat.

Common errors that lose marks:

• Blank or vague subject ("Hello", "Request") -- the busiest reader decides from the subject whether to open the mail.
• Wrong close pairing -- Dear Sir/Madam with Yours sincerely is a mismatch examiners notice.
• One giant paragraph -- break the body: purpose, facts, request.
• Missing facts -- a leave mail without dates, or an enquiry without roll number, gets no reply in real life and no marks in the exam.
• Demanding tone -- "I want leave" is an order; "I request leave" is a request. Offices answer requests.

4. Dialogue Writing

A dialogue is a conversation written as speech. It is not two essays cut into lines — question and answer must lock: if A asks for a day-pass, B either gives it or explains why not.

Rules:

• Situation first: one line of setting at the top is enough ("At the librarian's desk"). Do not print stage directions in every line.
• Names in the margin, then a colon, then the words spoken — Anil: Good afternoon…
• Short turns — each short enough to be said aloud in one breath.
• Natural speech: greetings, courtesy words, and one concrete detail (a rack, a register, a date) that puts the scene in a college, not a vacuum.
• Structure: open with a greeting or a need → develop with the facts → close with thanks or a next step.
• Punctuation: speech punctuated as ordinary sentences. Two speakers are enough unless the question asks for a group.

Punctuation of speech (the marks examiners check):

• Each new speaker starts a new line -- never run two speakers in one paragraph.
• Question mark and exclamation stay inside the spoken words ("Where should I leave my bag?").
• Keep reporting verbs light -- said, asked, replied are enough; fancy verbs sound comic in a college scene.

Bad vs good (one line each):
BAD: Anil: I want to know about the procedure that is followed for the issuance of a day-pass... -- an essay, not speech.
GOOD: Anil: I have left my identity card at home. May I still sit in the reading room? -- a person talking.

5. Report Writing

A report is a factual account of an event, a visit, or an inspection — written for a person who was not there. The voice is third-person or impersonal; a completed event is in the past tense; numbers, names and times are exact.

Standard format:

• Heading (title of the report).
• To / From / Date / Subject — four lines, always.
• Introduction — who asked, what was seen, when (2–3 lines).
• Findings — the body, in time order or from general to particular. Facts only.
• Conclusion — was the purpose met? (1–2 lines).
• Recommendations — only if asked for; opinion is labelled as advice, never mixed into findings as if it were fact.

Report vs blog: "The reading room opened in July" is a finding. "I felt peaceful there" is a blog line. Do not hide a problem in polite fog: "A leaking cooler wet a row of magazines last month; they have been dried and bound again" is a report sentence.

Types you may be asked for:

• Visit/inspection report -- what was seen (the model above).
• Event report -- what happened, in time order (a seminar, a match, a function).
• Progress/status note -- what is done, what remains.

Findings discipline: one fact per sentence; group related facts under mini-heads if the list is long (Seats / Hours / Rules); put the most important finding first. If a figure is approximate, say so ("about eighty seats") -- false precision ("79.5 seats") destroys trust.