'space' => '~' before \ref{} and \cite{}

Author: europ

doc1/doc.pdf

@@ -159,11 +159,11 @@ \section{Success of Open Source Projects}
 
     Who and what is the open source community? Sometimes the community is referred as anybody, sometimes it is restricted to the group of developers only. It depends, in some cases from the license itself too. We may consider, that the community is a group of people who are interested in the open source software, not just the developers of that software. Thereby, anybody related or connected to the usage, development, improvement or enhancement of the open source software can be considered as a member of the open source community. Because of the increasing interest for a software by absolutely anyone, the community has uncommonly fast grow, which has a positive affect on the software itself.\\
 
-    The community is strong, truly powerful. Together, collaboratively the community members are co-creating a single masterpiece of work, while they share their own intellectual properties as a subparts of the overall outcome. Many people are not just enhancing the pure software, but also their own skills. Learning new, yet unknown, things from the others can be considered as a benefit of being an open source community member. Do not forget to note that the community is worldwide in nature, so projects with larger scale are developed internationally such as projects listed in Table \ref{tab:open-source-projects}.
+    The community is strong, truly powerful. Together, collaboratively the community members are co-creating a single masterpiece of work, while they share their own intellectual properties as a subparts of the overall outcome. Many people are not just enhancing the pure software, but also their own skills. Learning new, yet unknown, things from the others can be considered as a benefit of being an open source community member. Do not forget to note that the community is worldwide in nature, so projects with larger scale are developed internationally such as projects listed in Table~\ref{tab:open-source-projects}.
 
     \subsection{Source Code Availability and Hosting}
 
-    To allow collaboration and contribution it is necessary to share the source code in some way as it is stated in the open source definition. In most cases these open source projects are using version control repositories or they may use something else, which are publicly hosted to make it available. Available version control repository hostings such as GitHub\footnote{\href{https://github.com/}{github.com}}, GitLab\footnote{\href{https://gitlab.com/}{gitlab.com}} or Bitbucket\footnote{\href{https://bitbucket.org/}{bitbucket.org}} are the most common ones. Their advantage is not only the management of change in the source code but also saving metadata such as related author, date of change and so on. Metadata might include information such as source code location, contributors, license, references and how to cite the software \cite{IEEE:OS-BP}. Using a properly configured version control repository with open access allows to save the derived works, authors of each modification and further requirements easily.
+    To allow collaboration and contribution it is necessary to share the source code in some way as it is stated in the open source definition. In most cases these open source projects are using version control repositories or they may use something else, which are publicly hosted to make it available. Available version control repository hostings such as GitHub\footnote{\href{https://github.com/}{github.com}}, GitLab\footnote{\href{https://gitlab.com/}{gitlab.com}} or Bitbucket\footnote{\href{https://bitbucket.org/}{bitbucket.org}} are the most common ones. Their advantage is not only the management of change in the source code but also saving metadata such as related author, date of change and so on. Metadata might include information such as source code location, contributors, license, references and how to cite the software~\cite{IEEE:OS-BP}. Using a properly configured version control repository with open access allows to save the derived works, authors of each modification and further requirements easily.
 
     \subsection{Collaboration and Contribution}
 
@@ -211,7 +211,7 @@ \section{The Open Systems}
 
     The open system are the outgrowth of the open source. Such systems form a set of open source softwares. As a practical example, note \textit{Apache Hadoop} framework or \textit{Elasticsearch} engine, which represent an open source system. A system with this scale is not easy to build, not even as an open source. To keep the software interoperability, scalability and simplicity it is needed to develop it in system parts (as smaller subsystems), which are together formulating one complex fully functional system.\\
 
-    We may consider the same pros and cons as it was listed in the Section \ref{FOSS:pros} and Section \ref{FOSS:cons} above for the FOSS. As it was noted that the open systems are derived from open source software, open systems pros and cons are slightly the same but the system complexity introduce some additional advantages and disadvantages. Those additional differences because of system size and complexity against open source software are included at proprietary software as well.
+    We may consider the same pros and cons as it was listed in the Section~\ref{FOSS:pros} and Section~\ref{FOSS:cons} above for the FOSS. As it was noted that the open systems are derived from open source software, open systems pros and cons are slightly the same but the system complexity introduce some additional advantages and disadvantages. Those additional differences because of system size and complexity against open source software are included at proprietary software as well.
 
 \newpage