Browse Source

org-contribute: Fix some typos

Change "Org-mode" to "Org mode" and insist on using two spaces after
full stops.
Nicolas Goaziou 11 months ago
parent
commit
29ba3c2407
1 changed files with 29 additions and 29 deletions
  1. 29 29
      org-contribute.org

+ 29 - 29
org-contribute.org

@@ -54,11 +54,11 @@ where your contribution will be useful:
   - The best way is to submit your code to [[file:org-mailing-list.org][the mailing list]] to discuss
     it with people.
   - If it is useful, you might consider contributing it to the
-    =lisp/contrib/= directory in the git repository. It will be
-    reviewed, and if it passes, it will be included. Ask help from
-    [[file:org-people.org][Eric Schulte]] for this step. The =lisp/contrib/= directory is somehow
-    relaxed: it is not distributed with Emacs, and does not require a
-    formal copyright assignment.
+    =lisp/contrib/= directory in the git repository.  It will be
+    reviewed, and if it passes, it will be included.  Ask help from
+    [[file:org-people.org][Eric Schulte]] for this step.  The =lisp/contrib/= directory is
+    somehow relaxed: it is not distributed with Emacs, and does not
+    require a formal copyright assignment.
   - If you decide to sign the [[*Copyright issues when contributing to Emacs Org mode][assignment contract with the FSF]], we
     might include your contribution in the distribution, and then in
     GNU Emacs.
@@ -75,13 +75,13 @@ contributing to these files, your first need to grant the right to
 include your works in GNU Emacs to the FSF.  For this you need to
 complete [[https://orgmode.org/request-assign-future.txt][this form]], and send it to [[mailto:assign@gnu.org][assign@gnu.org]].  The FSF will send
 you the assignment contract that both you and the FSF will sign.
-Please let the Org-mode maintainer know when this process is complete.
+Please let the Org mode maintainer know when this process is complete.
 Some people consider this assignment process a hassle.  I don't want
 to discuss this in detail here - there are some good reasons for
 getting the copyright registered, an example is discussed in this
 [[http://twit.tv/floss117][FLOSS weekly podcast]].  Furthermore, by playing according to the Emacs
 rules, we gain the fantastic advantage that every version of Emacs
-ships with Org-mode already fully built in.  So please consider doing
+ships with Org mode already fully built in.  So please consider doing
 this - it makes our work as maintainers so much easier, because we can
 then take your patches without any additional work.
 
@@ -90,7 +90,7 @@ collected, read this: [[http://www.gnu.org/licenses/why-assign.html][Why the FSF
 contributors?]]
 
 By submitting patches to emacs-orgmode@gnu.org, or by pushing changes
-to the Org-mode repository, you are placing these changes under the
+to the Org mode repository, you are placing these changes under the
 same licensing terms as those under which GNU Emacs is published.
 
 #+begin_example
@@ -102,8 +102,8 @@ same licensing terms as those under which GNU Emacs is published.
 
 If at the time you submit or push these changes you do have active
 copyright assignment papers with the FSF, for future changes to either
-Org-mode or to Emacs, this means that copyright to these changes is
-automatically transferred to the FSF.  The Org-mode repository is seen
+Org mode or to Emacs, this means that copyright to these changes is
+automatically transferred to the FSF.  The Org mode repository is seen
 as upstream repository for Emacs, anything contained in it can
 potentially end up in Emacs.  If you do not have signed papers with
 the FSF, only changes to files in the =contrib/= part of the repository
@@ -155,7 +155,7 @@ Lisp coding conventions]] described in Emacs manual.
 
 ** Sending patch with git
 
-Org-mode is developed using /git/ as the version control system.  Git
+Org mode is developed using /git/ as the version control system.  Git
 provides an amazing framework to collaborate on a project.  Git can be
 used to make patches and send them via email -- this is perfectly fine
 for major and minor changes.
@@ -229,7 +229,7 @@ through public branches of your repository clone.
    : git clone git@code.orgmode.org:bzg/org-mode.git
    : git clone https://code.orgmode.org/bzg/org-mode.git
 
-   The url using the git protocol is preferred. If you are behind a
+   The url using the git protocol is preferred.  If you are behind a
    firewall that blocks ~git://~, you can use the https url.
 
 2. Create a repository that can be publicly accessed, for example on
@@ -353,10 +353,10 @@ message and remove the indentation.
 :CUSTOM_ID: copyrighted-contributors
 :END:
 
-Here is the list of people who have contributed actual code to the
-Org-mode core.  Note that the manual contains a more extensive list
-with acknowledgments, including contributed ideas!  The lists below
-are mostly for house keeping, to help the maintainers keep track of
+Here is the list of people who have contributed actual code to the Org
+mode core.  Note that the manual contains a more extensive list with
+acknowledgments, including contributed ideas!  The lists below are
+mostly for house keeping, to help the maintainers keep track of
 copyright issues.
 
 ** Current contributors
@@ -411,7 +411,7 @@ within GNU Emacs:
 41. Clément Pit--Claudel
 42. Dan Davison
 43. Daniel M German
-44. Daniel M. Hackney
+44. Daniel M.\nbsp{}Hackney
 45. David Arroyo Menéndez
 46. David Maus
 47. David O'Toole
@@ -422,7 +422,7 @@ within GNU Emacs:
 52. Emmanuel Charpentier
 53. Eric Abrahamsen
 54. Eric Schulte
-55. Eric S. Fraga
+55. Eric S.\nbsp{}Fraga
 56. Erik Hetzner
 57. Erik Iverson
 58. Ethan Ligon
@@ -462,7 +462,7 @@ within GNU Emacs:
 92. Jonas Bernoulli
 93. Jonathan Leech-Pepin
 94. Jon Snader
-95. José L. Doménech
+95. José L.\nbsp{}Doménech
 96. Juan Pechiar
 97. Julian Gehring
 98. Julien Barnier
@@ -488,7 +488,7 @@ within GNU Emacs:
 118. Manuel Giraud
 119. Marcin Borkowski
 120. Marco Wahl
-121. Mark A. Hershberger
+121. Mark A.\nbsp{}Hershberger
 122. Martin Pohlack
 123. Martyn Jago
 124. Matt Lundin
@@ -497,7 +497,7 @@ within GNU Emacs:
 127. Michael Brand
 128. Michael Gauland
 129. Michael Sperber
-130. Miguel A. Figueroa-Villanueva
+130. Miguel A.\nbsp{}Figueroa-Villanueva
 131. Mikael Fornius
 132. Moritz Ulrich
 133. Nathaniel Flath
@@ -549,13 +549,13 @@ within GNU Emacs:
 179. Suvayu Ali
 180. Takaaki Ishikawa
 181. Tassilo Horn
-182. T.F. Torrey
+182. T.F.\nbsp{}Torrey
 183. Thibault Marin
 184. Thierry Banel
 185. Thomas Baumann
 186. Thomas Fitzsimmons
 187. Thomas Holst
-188. Thomas S. Dye
+188. Thomas S.\nbsp{}Dye
 189. Thorsten Jolitz
 190. Tim Burt
 191. Tim Landscheidt
@@ -573,7 +573,7 @@ within GNU Emacs:
 203. Yann Hodique
 204. Yasushi Shoji
 205. Yoshinari Nomura
-206. Yuri D. Lensky
+206. Yuri D.\nbsp{}Lensky
 207. Zhang Weize
 208. Zhuo Qingliang (Killy Draw)
 
@@ -595,7 +595,7 @@ without FSF papers.  When they submit more, we need to get papers
 eventually.  The limit is a cumulative change of 20 non-repetitive
 change lines.  Details are given in [[http://www.gnu.org/prep/maintain/maintain.html#Legally-Significant ][this document]].
 
-1. Aaron L. Zeng
+1. Aaron L.\nbsp{}Zeng
 2. Abhishek Chandratre
 3. Adam Aviv
 4. Aliaksey Artamonau
@@ -695,9 +695,9 @@ change lines.  Details are given in [[http://www.gnu.org/prep/maintain/maintain.
 98. Renato Ferreira
 99. Richard Hansen
 100. Richard Lawrence
-101. Richard Y. Kim (Kim)
+101. Richard Y.\nbsp{}Kim (Kim)
 102. Roberto Huelga
-103. Robert P. Goldman
+103. Robert P.\nbsp{}Goldman
 104. Roger Welsh
 105. Ruben Maher
 106. Sami Airaksinen
@@ -706,7 +706,7 @@ change lines.  Details are given in [[http://www.gnu.org/prep/maintain/maintain.
 109. Sergey Gordienko
 110. Sigmund Tzeng
 111. Stefano Rodighiero
-112. Stefan-W. Hahn
+112. Stefan-W.\nbsp{}Hahn
 113. Stig Brautaset
 114. Sylvain Chouleur
 115. Tadashi Hirata
@@ -727,7 +727,7 @@ change lines.  Details are given in [[http://www.gnu.org/prep/maintain/maintain.
 130. Xi Shen
 131. York Zhao
 132. Yue Zhu
-133. Zane D. Purvis
+133. Zane D.\nbsp{}Purvis
 134. Иван Трусков
 
 (This list may be incomplete - please help completing it.)