# How to contribute to edits on the website documentation **URL:** \ **Category:** Meta Elastic\ **Created:** [March 25, 2022, 2:12pm UTC](https://discuss.elastic.co/t/how-to-contribute-to-edits-on-the-website-documentation/300712 "2022-03-25T14:12:50Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![polarknight](https://avatars.discourse-cdn.com/v4/letter/p/a9a28c/32.png) [@polarknight](https://discuss.elastic.co/u/polarknight)\ **Post date:** [March 25, 2022, 2:12pm UTC](https://discuss.elastic.co/t/how-to-contribute-to-edits-on-the-website-documentation/300712/1 "2022-03-25T14:12:50Z")
Hi all, I hope this finds everyone well. I've been looking around but after, what I believe is incorrect as regards process, making a pull request for a documentation error on the [elastic.co](http://elastic.co) website for getting set up with a linux install. I've since scrapped the pull request and wanted to create it as an issue, as per the contribution guidelines. However, on your github, it appears to only focus on the following, or to create a blank issue: From [Sign in to GitHub · GitHub](https://github.com/elastic/elasticsearch/issues/new/choose) > **Bug** > > Report a confirmed bug. For unconfirmed bugs please visit [Elasticsearch - Discuss the Elastic Stack](https://discuss.elastic.co/c/elasticsearch) > > **Feature Request** > > Request a new feature we haven't thought of > > **Test Failure** > > A test failure in CI > > **Report a security vulnerability** > > Please review our security policy for more details > > **Question** > > Ask (and answer) questions here. I was wondering where the most correct location is to submit documentation on the website requests? Thanks in advance! ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 26, 2022, 4:39am UTC](https://discuss.elastic.co/t/how-to-contribute-to-edits-on-the-website-documentation/300712/2 "2022-03-26T04:39:38Z")
Could you share here the link of the page which has an issue? ---
**Author:** ![polarknight](https://avatars.discourse-cdn.com/v4/letter/p/a9a28c/32.png) [@polarknight](https://discuss.elastic.co/u/polarknight)\ **Post date:** [March 26, 2022, 5:12am UTC](https://discuss.elastic.co/t/how-to-contribute-to-edits-on-the-website-documentation/300712/3 "2022-03-26T05:12:40Z")
Hi David, On the page [Install Elasticsearch from archive on Linux or MacOS | Elasticsearch Guide [8.1] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/targz.html) Under "Check that Elasticsearch is running" The following: `curl --cacert $ES_PATH_CONF/certs/http_ca.crt -u elastic https://localhost:9200` Does not work. I believe it should now be: `curl --cacert $ES_PATH_CONF/config/certs/http_ca.crt -u elastic https://localhost:9200` Which does return the json as expected. Do let me know if you'd like more information! ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 26, 2022, 7:13am UTC](https://discuss.elastic.co/t/how-to-contribute-to-edits-on-the-website-documentation/300712/4 "2022-03-26T07:13:31Z")
Awesome. So could you just click on the edit button on that page? It will open [Sign in to GitHub · GitHub](https://github.com/elastic/elasticsearch/edit/8.1/docs/reference/setup/install/targz.asciidoc) where you can propose your changes. Would that work? Thanks again ---
**Author:** ![polarknight](https://avatars.discourse-cdn.com/v4/letter/p/a9a28c/32.png) [@polarknight](https://discuss.elastic.co/u/polarknight)\ **Post date:** [March 26, 2022, 8:12am UTC](https://discuss.elastic.co/t/how-to-contribute-to-edits-on-the-website-documentation/300712/5 "2022-03-26T08:12:33Z")
Hi David, I did create a pull request, but this is out of the normal protocol for how to submit these items so I removed it and opened this post, since there seems to be a process for submitting items as an issue before creating a pull request. If just creating a pull request is the correct way to approach this, I can recreate it if so? I just want to make sure I'm not causing someone a headache by performing the wrong action - documentation is an area that I've found every project has their own approach to! ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 26, 2022, 1:45pm UTC](https://discuss.elastic.co/t/how-to-contribute-to-edits-on-the-website-documentation/300712/6 "2022-03-26T13:45:17Z")
Yes. Please open a PR for this. 😉 ---
**Author:** ![polarknight](https://avatars.discourse-cdn.com/v4/letter/p/a9a28c/32.png) [@polarknight](https://discuss.elastic.co/u/polarknight)\ **Post date:** [March 26, 2022, 1:55pm UTC](https://discuss.elastic.co/t/how-to-contribute-to-edits-on-the-website-documentation/300712/7 "2022-03-26T13:55:18Z")
Done! Thank you for your help, the request is #85364. If anything amiss, do let me know! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 23, 2022, 1:55pm UTC](https://discuss.elastic.co/t/how-to-contribute-to-edits-on-the-website-documentation/300712/8 "2022-04-23T13:55:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.