Skip to content

Commit 6578e8f

Browse files
authored
Revise wording for clarity in why.md
1 parent 2135de4 commit 6578e8f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/why.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Publishing a job on **multiple portals** often means to *copy/paste* data and **
2828

2929
It is **not obvious to find the criteria** to decide on which portal they have the best chances to find a candidate.
3030

31-
We think, this is rediculous unneccessary: As an employer we want to publish the job on **one location** and **spread** the info.
31+
We find this unnecessary and impractical: as employers, we want to advertise the position in **one place** and **distribute** the information.
3232

3333
We think, our solution might be the missing piece to make it work.
3434

@@ -40,4 +40,4 @@ While there has been some attempts to address this using a job posting schema fo
4040

4141
We propose a much simpler approach, **inspired by conventions** like robots.txt or sitemap.xml. Companies would place all their job listings in a structured file at a single, well-known URL.
4242

43-
Job search engines and aggregators would only need to check this one location to get all the data they need. This would make discovering and indexing job postings vastly more efficient for everyone.
43+
Job search engines and aggregators would only need to check this one location to get all the data they need. This would make discovering and indexing job postings vastly more efficient for everyone.

0 commit comments

Comments
 (0)