Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs]: Grammatical mistake in documentation for local installation #6552

Closed
Haider8 opened this issue Oct 26, 2019 · 6 comments · Fixed by #6568
Closed

[Docs]: Grammatical mistake in documentation for local installation #6552

Haider8 opened this issue Oct 26, 2019 · 6 comments · Fixed by #6568

Comments

@Haider8
Copy link
Contributor

Haider8 commented Oct 26, 2019

Describe the bug

A grammatical mistake in the documentation for the local installation of the project.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://github.com/fossasia/open-event-server/blob/development/docs/installation/local.md#using-pipenv'
  2. Scroll down to 'Step 2'
  3. See error, Go the directory where your postgres file is stored

Expected behavior

Go to the directory where your Postgres file is stored

Stacktrace

Additional details (please complete the following information):

  • OS: [e.g. MacOS, Ubuntu, CentOS]
  • Python Version [e.g. 3.5, 3.6]
  • HEAD Commit hash [e.g. 4629c62]

Additional context

Want to work on this

@iamareebjamal
Copy link
Member

p->P is not a grammatical mistake. Besides, postgres is not wrong

@iamareebjamal
Copy link
Member

OK, to is missing

@Samiksha99
Copy link

I would like to work on this issue

@Haider8
Copy link
Contributor Author

Haider8 commented Oct 29, 2019

@Samiksha99 Sure, go ahead.

@nnrepos
Copy link
Contributor

nnrepos commented Nov 2, 2019

Since this hasn't been done in a while, I'll do it instead. I think it would've been wiser to approve @snitin315's commit by the way.

nnrepos added a commit to nnrepos/open-event-server that referenced this issue Nov 2, 2019
@prateekj117
Copy link
Member

@nnrepos It's a documentation issue and not an urgent one. And it's important for a newcomer to know how things should go so that no two developers work on the same issue. Though it has been a few days and there has been no PR from @Samiksha99, you can go ahead with this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants