Repository: orc Updated Branches: refs/heads/master 449fb6328 -> ee95f6cb4
Fixed spelling in site. Fixes #297 Signed-off-by: Owen O'Malley <omal...@apache.org> Project: http://git-wip-us.apache.org/repos/asf/orc/repo Commit: http://git-wip-us.apache.org/repos/asf/orc/commit/ee95f6cb Tree: http://git-wip-us.apache.org/repos/asf/orc/tree/ee95f6cb Diff: http://git-wip-us.apache.org/repos/asf/orc/diff/ee95f6cb Branch: refs/heads/master Commit: ee95f6cb4a31c316815d9e33523186e27d3067dd Parents: 449fb63 Author: Jimmy Casey <casey.ji...@gmail.com> Authored: Sun Jul 29 21:47:03 2018 +0000 Committer: Owen O'Malley <omal...@apache.org> Committed: Mon Aug 6 14:19:58 2018 -0700 ---------------------------------------------------------------------- site/_posts/2016-06-28-file-format-talk.md | 2 +- site/security/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/orc/blob/ee95f6cb/site/_posts/2016-06-28-file-format-talk.md ---------------------------------------------------------------------- diff --git a/site/_posts/2016-06-28-file-format-talk.md b/site/_posts/2016-06-28-file-format-talk.md index 5cf6574..4bd95f6 100644 --- a/site/_posts/2016-06-28-file-format-talk.md +++ b/site/_posts/2016-06-28-file-format-talk.md @@ -8,7 +8,7 @@ categories: [talk] I gave a talk at Hadoop Summit San Jose 2016 about a file format benchmark that I've contributed as [ORC-72]({{site.jira}}/ORC-72). The -benchmark focuses on real data sets that are publically available. The data +benchmark focuses on real data sets that are publicly available. The data sets represent a wide variety of use cases: * *NYC Taxi Data* - very dense data with mostly numeric types http://git-wip-us.apache.org/repos/asf/orc/blob/ee95f6cb/site/security/index.md ---------------------------------------------------------------------- diff --git a/site/security/index.md b/site/security/index.md index 497d1fc..6c1f087 100644 --- a/site/security/index.md +++ b/site/security/index.md @@ -38,7 +38,7 @@ An overview of the vulnerability handling process is: * The reporter sends email to the project privately. * The project works privately with the reporter to resolve the vulnerability. * The project releases a new version that includes the fix. -* The vulnerability is publically announced via a [CVE](https://cve.mitre.org/) to the mailing lists and the original reporter. +* The vulnerability is publicly announced via a [CVE](https://cve.mitre.org/) to the mailing lists and the original reporter. The full process can be found on the [Apache Security Process](https://www.apache.org/security/committers.html#vulnerability-handling) page.
