format: apply repo prettier (3.8.1) to the folded skills tree
963 markdown files reformatted with the repository's pinned prettier so pnpm format:check covers the folded tree like every other repo file. The formatter's embedded-language pass also normalized code fences (TS semicolons, closed HTML tags in examples, lowercased CSS hex colors, one renumbered list that skipped an index). Alphanumeric token deltas vs the fold commit were audited file-by-file; all are formatter-equivalent markup normalizations plus the four sanitized skills.
This commit is contained in:
@@ -35,6 +35,7 @@ Before auditing, understand:
|
||||
## Audit Framework
|
||||
|
||||
### Priority Order
|
||||
|
||||
1. **Crawlability & Indexation** (can Google find and index it?)
|
||||
2. **Technical Foundations** (is the site fast and functional?)
|
||||
3. **On-Page Optimization** (is content optimized?)
|
||||
@@ -48,11 +49,13 @@ Before auditing, understand:
|
||||
### Crawlability
|
||||
|
||||
**Robots.txt**
|
||||
|
||||
- Check for unintentional blocks
|
||||
- Verify important pages allowed
|
||||
- Check sitemap reference
|
||||
|
||||
**XML Sitemap**
|
||||
|
||||
- Exists and accessible
|
||||
- Submitted to Search Console
|
||||
- Contains only canonical, indexable URLs
|
||||
@@ -60,12 +63,14 @@ Before auditing, understand:
|
||||
- Proper formatting
|
||||
|
||||
**Site Architecture**
|
||||
|
||||
- Important pages within 3 clicks of homepage
|
||||
- Logical hierarchy
|
||||
- Internal linking structure
|
||||
- No orphan pages
|
||||
|
||||
**Crawl Budget Issues** (for large sites)
|
||||
|
||||
- Parameterized URLs under control
|
||||
- Faceted navigation handled properly
|
||||
- Infinite scroll with pagination fallback
|
||||
@@ -74,11 +79,13 @@ Before auditing, understand:
|
||||
### Indexation
|
||||
|
||||
**Index Status**
|
||||
|
||||
- site:domain.com check
|
||||
- Search Console coverage report
|
||||
- Compare indexed vs. expected
|
||||
|
||||
**Indexation Issues**
|
||||
|
||||
- Noindex tags on important pages
|
||||
- Canonicals pointing wrong direction
|
||||
- Redirect chains/loops
|
||||
@@ -86,6 +93,7 @@ Before auditing, understand:
|
||||
- Duplicate content without canonicals
|
||||
|
||||
**Canonicalization**
|
||||
|
||||
- All pages have canonical tags
|
||||
- Self-referencing canonicals on unique pages
|
||||
- HTTP → HTTPS canonicals
|
||||
@@ -95,11 +103,13 @@ Before auditing, understand:
|
||||
### Site Speed & Core Web Vitals
|
||||
|
||||
**Core Web Vitals**
|
||||
|
||||
- LCP (Largest Contentful Paint): < 2.5s
|
||||
- INP (Interaction to Next Paint): < 200ms
|
||||
- CLS (Cumulative Layout Shift): < 0.1
|
||||
|
||||
**Speed Factors**
|
||||
|
||||
- Server response time (TTFB)
|
||||
- Image optimization
|
||||
- JavaScript execution
|
||||
@@ -109,6 +119,7 @@ Before auditing, understand:
|
||||
- Font loading
|
||||
|
||||
**Tools**
|
||||
|
||||
- PageSpeed Insights
|
||||
- WebPageTest
|
||||
- Chrome DevTools
|
||||
@@ -146,6 +157,7 @@ Before auditing, understand:
|
||||
### Title Tags
|
||||
|
||||
**Check for:**
|
||||
|
||||
- Unique titles for each page
|
||||
- Primary keyword near beginning
|
||||
- 50-60 characters (visible in SERP)
|
||||
@@ -153,6 +165,7 @@ Before auditing, understand:
|
||||
- Brand name placement (end, usually)
|
||||
|
||||
**Common issues:**
|
||||
|
||||
- Duplicate titles
|
||||
- Too long (truncated)
|
||||
- Too short (wasted opportunity)
|
||||
@@ -162,6 +175,7 @@ Before auditing, understand:
|
||||
### Meta Descriptions
|
||||
|
||||
**Check for:**
|
||||
|
||||
- Unique descriptions per page
|
||||
- 150-160 characters
|
||||
- Includes primary keyword
|
||||
@@ -169,6 +183,7 @@ Before auditing, understand:
|
||||
- Call to action
|
||||
|
||||
**Common issues:**
|
||||
|
||||
- Duplicate descriptions
|
||||
- Auto-generated garbage
|
||||
- Too long/short
|
||||
@@ -177,6 +192,7 @@ Before auditing, understand:
|
||||
### Heading Structure
|
||||
|
||||
**Check for:**
|
||||
|
||||
- One H1 per page
|
||||
- H1 contains primary keyword
|
||||
- Logical hierarchy (H1 → H2 → H3)
|
||||
@@ -184,6 +200,7 @@ Before auditing, understand:
|
||||
- Not just for styling
|
||||
|
||||
**Common issues:**
|
||||
|
||||
- Multiple H1s
|
||||
- Skip levels (H1 → H3)
|
||||
- Headings used for styling only
|
||||
@@ -192,6 +209,7 @@ Before auditing, understand:
|
||||
### Content Optimization
|
||||
|
||||
**Primary Page Content**
|
||||
|
||||
- Keyword in first 100 words
|
||||
- Related keywords naturally used
|
||||
- Sufficient depth/length for topic
|
||||
@@ -199,6 +217,7 @@ Before auditing, understand:
|
||||
- Better than competitors
|
||||
|
||||
**Thin Content Issues**
|
||||
|
||||
- Pages with little unique content
|
||||
- Tag/category pages with no value
|
||||
- Doorway pages
|
||||
@@ -207,6 +226,7 @@ Before auditing, understand:
|
||||
### Image Optimization
|
||||
|
||||
**Check for:**
|
||||
|
||||
- Descriptive file names
|
||||
- Alt text on all images
|
||||
- Alt text describes image
|
||||
@@ -218,6 +238,7 @@ Before auditing, understand:
|
||||
### Internal Linking
|
||||
|
||||
**Check for:**
|
||||
|
||||
- Important pages well-linked
|
||||
- Descriptive anchor text
|
||||
- Logical link relationships
|
||||
@@ -225,6 +246,7 @@ Before auditing, understand:
|
||||
- Reasonable link count per page
|
||||
|
||||
**Common issues:**
|
||||
|
||||
- Orphan pages (no internal links)
|
||||
- Over-optimized anchor text
|
||||
- Important pages buried
|
||||
@@ -233,12 +255,14 @@ Before auditing, understand:
|
||||
### Keyword Targeting
|
||||
|
||||
**Per Page**
|
||||
|
||||
- Clear primary keyword target
|
||||
- Title, H1, URL aligned
|
||||
- Content satisfies search intent
|
||||
- Not competing with other pages (cannibalization)
|
||||
|
||||
**Site-Wide**
|
||||
|
||||
- Keyword mapping document
|
||||
- No major gaps in coverage
|
||||
- No keyword cannibalization
|
||||
@@ -251,21 +275,25 @@ Before auditing, understand:
|
||||
### E-E-A-T Signals
|
||||
|
||||
**Experience**
|
||||
|
||||
- First-hand experience demonstrated
|
||||
- Original insights/data
|
||||
- Real examples and case studies
|
||||
|
||||
**Expertise**
|
||||
|
||||
- Author credentials visible
|
||||
- Accurate, detailed information
|
||||
- Properly sourced claims
|
||||
|
||||
**Authoritativeness**
|
||||
|
||||
- Recognized in the space
|
||||
- Cited by others
|
||||
- Industry credentials
|
||||
|
||||
**Trustworthiness**
|
||||
|
||||
- Accurate information
|
||||
- Transparent about business
|
||||
- Contact information available
|
||||
@@ -291,6 +319,7 @@ Before auditing, understand:
|
||||
## Common Issues by Site Type
|
||||
|
||||
### SaaS/Product Sites
|
||||
|
||||
- Product pages lack content depth
|
||||
- Blog not integrated with product pages
|
||||
- Missing comparison/alternative pages
|
||||
@@ -298,6 +327,7 @@ Before auditing, understand:
|
||||
- No glossary/educational content
|
||||
|
||||
### E-commerce
|
||||
|
||||
- Thin category pages
|
||||
- Duplicate product descriptions
|
||||
- Missing product schema
|
||||
@@ -305,6 +335,7 @@ Before auditing, understand:
|
||||
- Out-of-stock pages mishandled
|
||||
|
||||
### Content/Blog Sites
|
||||
|
||||
- Outdated content not refreshed
|
||||
- Keyword cannibalization
|
||||
- No topical clustering
|
||||
@@ -312,6 +343,7 @@ Before auditing, understand:
|
||||
- Missing author pages
|
||||
|
||||
### Local Business
|
||||
|
||||
- Inconsistent NAP
|
||||
- Missing local schema
|
||||
- No Google Business Profile optimization
|
||||
@@ -325,12 +357,14 @@ Before auditing, understand:
|
||||
### Audit Report Structure
|
||||
|
||||
**Executive Summary**
|
||||
|
||||
- Overall health assessment
|
||||
- Top 3-5 priority issues
|
||||
- Quick wins identified
|
||||
|
||||
**Technical SEO Findings**
|
||||
For each issue:
|
||||
|
||||
- **Issue**: What's wrong
|
||||
- **Impact**: SEO impact (High/Medium/Low)
|
||||
- **Evidence**: How you found it
|
||||
@@ -344,6 +378,7 @@ Same format as above
|
||||
Same format as above
|
||||
|
||||
**Prioritized Action Plan**
|
||||
|
||||
1. Critical fixes (blocking indexation/ranking)
|
||||
2. High-impact improvements
|
||||
3. Quick wins (easy, immediate benefit)
|
||||
@@ -361,6 +396,7 @@ Same format as above
|
||||
## Tools Referenced
|
||||
|
||||
**Free Tools**
|
||||
|
||||
- Google Search Console (essential)
|
||||
- Google PageSpeed Insights
|
||||
- Bing Webmaster Tools
|
||||
@@ -369,6 +405,7 @@ Same format as above
|
||||
- Schema Validator
|
||||
|
||||
**Paid Tools** (if available)
|
||||
|
||||
- Screaming Frog
|
||||
- Ahrefs / Semrush
|
||||
- Sitebulb
|
||||
|
||||
@@ -19,6 +19,7 @@ Use for "What is [X]?" queries.
|
||||
```
|
||||
|
||||
**Example:**
|
||||
|
||||
```markdown
|
||||
## What is Answer Engine Optimization?
|
||||
|
||||
@@ -44,6 +45,7 @@ Use for "How to [X]" queries. Optimal for list snippets.
|
||||
```
|
||||
|
||||
**Example:**
|
||||
|
||||
```markdown
|
||||
## How to Optimize Content for Featured Snippets
|
||||
|
||||
@@ -65,13 +67,13 @@ Use for "[X] vs [Y]" queries. Optimal for table snippets.
|
||||
```markdown
|
||||
## [Option A] vs [Option B]: [Brief Descriptor]
|
||||
|
||||
| Feature | [Option A] | [Option B] |
|
||||
|---------|------------|------------|
|
||||
| Feature | [Option A] | [Option B] |
|
||||
| ------------ | ------------------- | ------------------- |
|
||||
| [Criteria 1] | [Value/Description] | [Value/Description] |
|
||||
| [Criteria 2] | [Value/Description] | [Value/Description] |
|
||||
| [Criteria 3] | [Value/Description] | [Value/Description] |
|
||||
| [Criteria 4] | [Value/Description] | [Value/Description] |
|
||||
| Best For | [Use case] | [Use case] |
|
||||
| Best For | [Use case] | [Use case] |
|
||||
|
||||
**Bottom line**: [1-2 sentence recommendation based on different needs]
|
||||
```
|
||||
@@ -121,6 +123,7 @@ Use for topic pages with multiple common questions. Essential for FAQ schema.
|
||||
```
|
||||
|
||||
**Tips for FAQ questions:**
|
||||
|
||||
- Use natural question phrasing ("How do I..." not "How does one...")
|
||||
- Include question words: what, how, why, when, where, who, which
|
||||
- Match "People Also Ask" queries from search results
|
||||
@@ -163,6 +166,7 @@ Statistics increase AI citation rates by 15-30%. Always include sources.
|
||||
```
|
||||
|
||||
**Example:**
|
||||
|
||||
```markdown
|
||||
Mobile optimization is no longer optional for SEO success. According to Google's 2024 Core Web Vitals report, 70% of web traffic now comes from mobile devices, and pages failing mobile usability standards see 24% higher bounce rates. This makes mobile-first indexing a critical ranking factor.
|
||||
```
|
||||
@@ -176,6 +180,7 @@ Named expert attribution adds credibility and increases citation likelihood.
|
||||
```
|
||||
|
||||
**Example:**
|
||||
|
||||
```markdown
|
||||
"The shift from keyword-driven search to intent-driven discovery represents the most significant change in SEO since mobile-first indexing," says Rand Fishkin, Co-founder of SparkToro. This perspective highlights why content strategies must evolve beyond traditional keyword optimization.
|
||||
```
|
||||
@@ -189,6 +194,7 @@ Structure claims for easy AI extraction with clear attribution.
|
||||
```
|
||||
|
||||
**Example:**
|
||||
|
||||
```markdown
|
||||
E-E-A-T is the cornerstone of Google's content quality evaluation. Google's Search Quality Rater Guidelines confirm that trust is the most critical factor, stating that "untrustworthy pages have low E-E-A-T no matter how experienced, expert, or authoritative they may seem." This means content creators must prioritize transparency and accuracy above all other optimization tactics.
|
||||
```
|
||||
@@ -202,6 +208,7 @@ Create quotable, standalone statements that AI can extract directly.
|
||||
```
|
||||
|
||||
**Example:**
|
||||
|
||||
```markdown
|
||||
**Ideal blog post length for SEO**: The optimal length for SEO blog posts is 1,500-2,500 words for competitive topics. This range allows comprehensive topic coverage while maintaining reader engagement. HubSpot research shows long-form content earns 77% more backlinks than short articles, directly impacting search rankings.
|
||||
```
|
||||
@@ -214,6 +221,7 @@ Structure claims with evidence for maximum credibility.
|
||||
[Opening claim statement].
|
||||
|
||||
Evidence supporting this includes:
|
||||
|
||||
- [Data point 1 with source]
|
||||
- [Data point 2 with source]
|
||||
- [Data point 3 with source]
|
||||
@@ -228,30 +236,35 @@ Evidence supporting this includes:
|
||||
Different content domains benefit from different authority signals.
|
||||
|
||||
### Technology Content
|
||||
|
||||
- Emphasize technical precision and correct terminology
|
||||
- Include version numbers and dates for software/tools
|
||||
- Reference official documentation
|
||||
- Add code examples where relevant
|
||||
|
||||
### Health/Medical Content
|
||||
|
||||
- Cite peer-reviewed studies with publication details
|
||||
- Include expert credentials (MD, RN, etc.)
|
||||
- Note study limitations and context
|
||||
- Add "last reviewed" dates
|
||||
|
||||
### Financial Content
|
||||
|
||||
- Reference regulatory bodies (SEC, FTC, etc.)
|
||||
- Include specific numbers with timeframes
|
||||
- Note that information is educational, not advice
|
||||
- Cite recognized financial institutions
|
||||
|
||||
### Legal Content
|
||||
|
||||
- Cite specific laws, statutes, and regulations
|
||||
- Reference jurisdiction clearly
|
||||
- Include professional disclaimers
|
||||
- Note when professional consultation is advised
|
||||
|
||||
### Business/Marketing Content
|
||||
|
||||
- Include case studies with measurable results
|
||||
- Reference industry research and reports
|
||||
- Add percentage changes and timeframes
|
||||
@@ -264,6 +277,7 @@ Different content domains benefit from different authority signals.
|
||||
Voice queries are conversational and question-based. Optimize for these patterns:
|
||||
|
||||
### Question Formats for Voice
|
||||
|
||||
- "What is..."
|
||||
- "How do I..."
|
||||
- "Where can I find..."
|
||||
@@ -272,6 +286,7 @@ Voice queries are conversational and question-based. Optimize for these patterns
|
||||
- "Who is..."
|
||||
|
||||
### Voice-Optimized Answer Structure
|
||||
|
||||
- Lead with direct answer (under 30 words ideal)
|
||||
- Use natural, conversational language
|
||||
- Avoid jargon unless targeting expert audience
|
||||
|
||||
@@ -13,20 +13,23 @@ Sources: Grammarly (2025), Microsoft 365 Life Hacks (2025), GPTHuman (2025), Wal
|
||||
Em dashes are longer than hyphens (-) and are used for emphasis, interruptions, or parenthetical information. While they have legitimate uses in writing, AI models drastically overuse them.
|
||||
|
||||
### Why Em Dashes Signal AI Writing
|
||||
|
||||
- AI models were trained on edited books, academic papers, and style guides where em dashes appear frequently
|
||||
- AI uses em dashes as a shortcut for sentence variety instead of commas, colons, or parentheses
|
||||
- Most human writers rarely use em dashes because they don't exist as a standard keyboard key
|
||||
- The overuse is so consistent that it has become the unofficial signature of ChatGPT writing
|
||||
|
||||
### What To Do Instead
|
||||
| Instead of | Use |
|
||||
|------------|-----|
|
||||
| The results—which were surprising—showed... | The results, which were surprising, showed... |
|
||||
| This approach—unlike traditional methods—allows... | This approach, unlike traditional methods, allows... |
|
||||
| The study found—as expected—that... | The study found, as expected, that... |
|
||||
|
||||
| Instead of | Use |
|
||||
| ---------------------------------------------------------- | ------------------------------------------------------------ |
|
||||
| The results—which were surprising—showed... | The results, which were surprising, showed... |
|
||||
| This approach—unlike traditional methods—allows... | This approach, unlike traditional methods, allows... |
|
||||
| The study found—as expected—that... | The study found, as expected, that... |
|
||||
| Communication skills—both written and verbal—are essential | Communication skills (both written and verbal) are essential |
|
||||
|
||||
### Guidelines
|
||||
|
||||
- Use commas for most parenthetical information
|
||||
- Use colons to introduce explanations or lists
|
||||
- Use parentheses for supplementary information
|
||||
@@ -37,67 +40,68 @@ Em dashes are longer than hyphens (-) and are used for emphasis, interruptions,
|
||||
|
||||
## Overused Verbs
|
||||
|
||||
| Avoid | Use Instead |
|
||||
|-------|-------------|
|
||||
| Avoid | Use Instead |
|
||||
| ------------ | -------------------------------------- |
|
||||
| delve (into) | explore, examine, investigate, look at |
|
||||
| leverage | use, apply, draw on |
|
||||
| optimise | improve, refine, enhance |
|
||||
| utilise | use |
|
||||
| facilitate | help, enable, support |
|
||||
| foster | encourage, support, develop, nurture |
|
||||
| bolster | strengthen, support, reinforce |
|
||||
| underscore | emphasise, highlight, stress |
|
||||
| unveil | reveal, show, introduce, present |
|
||||
| navigate | manage, handle, work through |
|
||||
| streamline | simplify, make more efficient |
|
||||
| enhance | improve, strengthen |
|
||||
| endeavour | try, attempt, effort |
|
||||
| ascertain | find out, determine, establish |
|
||||
| elucidate | explain, clarify, make clear |
|
||||
| leverage | use, apply, draw on |
|
||||
| optimise | improve, refine, enhance |
|
||||
| utilise | use |
|
||||
| facilitate | help, enable, support |
|
||||
| foster | encourage, support, develop, nurture |
|
||||
| bolster | strengthen, support, reinforce |
|
||||
| underscore | emphasise, highlight, stress |
|
||||
| unveil | reveal, show, introduce, present |
|
||||
| navigate | manage, handle, work through |
|
||||
| streamline | simplify, make more efficient |
|
||||
| enhance | improve, strengthen |
|
||||
| endeavour | try, attempt, effort |
|
||||
| ascertain | find out, determine, establish |
|
||||
| elucidate | explain, clarify, make clear |
|
||||
|
||||
---
|
||||
|
||||
## Overused Adjectives
|
||||
|
||||
| Avoid | Use Instead |
|
||||
|-------|-------------|
|
||||
| robust | strong, reliable, thorough, solid |
|
||||
| comprehensive | complete, thorough, full, detailed |
|
||||
| pivotal | key, critical, central, important |
|
||||
| crucial | important, key, essential, critical |
|
||||
| vital | important, essential, necessary |
|
||||
| transformative | significant, important, major |
|
||||
| cutting-edge | new, advanced, recent, modern |
|
||||
| groundbreaking | new, original, significant |
|
||||
| innovative | new, original, creative |
|
||||
| seamless | smooth, easy, effortless |
|
||||
| intricate | complex, detailed, complicated |
|
||||
| nuanced | subtle, complex, detailed |
|
||||
| multifaceted | complex, varied, diverse |
|
||||
| holistic | complete, whole, comprehensive |
|
||||
| Avoid | Use Instead |
|
||||
| -------------- | ----------------------------------- |
|
||||
| robust | strong, reliable, thorough, solid |
|
||||
| comprehensive | complete, thorough, full, detailed |
|
||||
| pivotal | key, critical, central, important |
|
||||
| crucial | important, key, essential, critical |
|
||||
| vital | important, essential, necessary |
|
||||
| transformative | significant, important, major |
|
||||
| cutting-edge | new, advanced, recent, modern |
|
||||
| groundbreaking | new, original, significant |
|
||||
| innovative | new, original, creative |
|
||||
| seamless | smooth, easy, effortless |
|
||||
| intricate | complex, detailed, complicated |
|
||||
| nuanced | subtle, complex, detailed |
|
||||
| multifaceted | complex, varied, diverse |
|
||||
| holistic | complete, whole, comprehensive |
|
||||
|
||||
---
|
||||
|
||||
## Overused Transitions and Connectors
|
||||
|
||||
| Avoid | Use Instead |
|
||||
|-------|-------------|
|
||||
| furthermore | also, in addition, and |
|
||||
| moreover | also, and, besides |
|
||||
| notwithstanding | despite, even so, still |
|
||||
| that being said | however, but, still |
|
||||
| at its core | essentially, fundamentally, basically |
|
||||
| to put it simply | in short, simply put |
|
||||
| it is worth noting that | note that, importantly |
|
||||
| in the realm of | in, within, regarding |
|
||||
| in the landscape of | in, within |
|
||||
| in today's [anything] | currently, now, today |
|
||||
| Avoid | Use Instead |
|
||||
| ----------------------- | ------------------------------------- |
|
||||
| furthermore | also, in addition, and |
|
||||
| moreover | also, and, besides |
|
||||
| notwithstanding | despite, even so, still |
|
||||
| that being said | however, but, still |
|
||||
| at its core | essentially, fundamentally, basically |
|
||||
| to put it simply | in short, simply put |
|
||||
| it is worth noting that | note that, importantly |
|
||||
| in the realm of | in, within, regarding |
|
||||
| in the landscape of | in, within |
|
||||
| in today's [anything] | currently, now, today |
|
||||
|
||||
---
|
||||
|
||||
## Phrases That Signal AI Writing
|
||||
|
||||
### Opening Phrases to Avoid
|
||||
|
||||
- "In today's fast-paced world..."
|
||||
- "In today's digital age..."
|
||||
- "In an era of..."
|
||||
@@ -108,6 +112,7 @@ Em dashes are longer than hyphens (-) and are used for emphasis, interruptions,
|
||||
- "Imagine a world where..."
|
||||
|
||||
### Transitional Phrases to Avoid
|
||||
|
||||
- "That being said..."
|
||||
- "With that in mind..."
|
||||
- "It's worth mentioning that..."
|
||||
@@ -117,6 +122,7 @@ Em dashes are longer than hyphens (-) and are used for emphasis, interruptions,
|
||||
- "This begs the question..."
|
||||
|
||||
### Concluding Phrases to Avoid
|
||||
|
||||
- "In conclusion..."
|
||||
- "To sum up..."
|
||||
- "By [doing X], you can [achieve Y]..."
|
||||
@@ -125,6 +131,7 @@ Em dashes are longer than hyphens (-) and are used for emphasis, interruptions,
|
||||
- "At the end of the day..."
|
||||
|
||||
### Structural Patterns to Avoid
|
||||
|
||||
- "Whether you're a [X], [Y], or [Z]..." (listing three examples after "whether")
|
||||
- "It's not just [X], it's also [Y]..."
|
||||
- "Think of [X] as [elaborate metaphor]..."
|
||||
@@ -163,20 +170,20 @@ These words often add nothing to meaning. Remove them or find specific alternati
|
||||
|
||||
## Academic-Specific AI Tells
|
||||
|
||||
| Avoid | Use Instead |
|
||||
|-------|-------------|
|
||||
| shed light on | clarify, explain, reveal |
|
||||
| pave the way for | enable, allow, make possible |
|
||||
| a myriad of | many, numerous, various |
|
||||
| a plethora of | many, numerous, several |
|
||||
| paramount | very important, essential, critical |
|
||||
| pertaining to | about, regarding, concerning |
|
||||
| prior to | before |
|
||||
| subsequent to | after |
|
||||
| in light of | because of, given, considering |
|
||||
| with respect to | about, regarding, for |
|
||||
| in terms of | regarding, for, about |
|
||||
| the fact that | that (or rewrite sentence) |
|
||||
| Avoid | Use Instead |
|
||||
| ---------------- | ----------------------------------- |
|
||||
| shed light on | clarify, explain, reveal |
|
||||
| pave the way for | enable, allow, make possible |
|
||||
| a myriad of | many, numerous, various |
|
||||
| a plethora of | many, numerous, several |
|
||||
| paramount | very important, essential, critical |
|
||||
| pertaining to | about, regarding, concerning |
|
||||
| prior to | before |
|
||||
| subsequent to | after |
|
||||
| in light of | because of, given, considering |
|
||||
| with respect to | about, regarding, for |
|
||||
| in terms of | regarding, for, about |
|
||||
| the fact that | that (or rewrite sentence) |
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user