@@ -4,7 +4,7 @@ Documentation Practices
4
4
=======================
5
5
PyAnsys documentation must not only be written but also maintained. If you are
6
6
new to writing developer documentation, see the `Google Developer Documentation
7
- Style Guide <https://developers.google.com/style/articles > `_. It provides
7
+ Style Guide <https://developers.google.com/style> `_. It provides
8
8
editorial guidelines for writing clear and consistent developer documentation,
9
9
allowing this guide to supply guidance specific to PyAnsys library
10
10
documentation.
@@ -186,7 +186,7 @@ Cloning a GitHub Repository
186
186
---------------------------
187
187
Contributing to a GitHub repository requires that you first clone the repository. While developers
188
188
likely know many ways to do this, technical documentation specialists may need to review the
189
- following instructions for using either Windows PowerShell or GitBash to clone a GitHub repository.
189
+ following instructions for using either Windows PowerShell or Git Bash to clone a GitHub repository.
190
190
191
191
Using Windows PowerShell to Clone a GitHub Repository
192
192
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -218,12 +218,12 @@ To use Windows PowerShell to clone a GitHub repository:
218
218
.. note ::
219
219
In PowerShell, typing ``dir `` is the equivalent to typing ``ls ``.
220
220
221
- Using GitBash to Clone a GitHub Repository
222
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
223
- To use GitBash to clone a GitHub repository:
221
+ Using Git Bash to Clone a GitHub Repository
222
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
223
+ To use Git Bash to clone a GitHub repository:
224
224
225
225
#. In the directory where you want to clone PyAnsys repositories, right-click and
226
- select ``GitBash Here ``.
226
+ select ``Git Bash Here ``.
227
227
228
228
#. Type ``git clone `` followed by the address of the repo to clone.
229
229
@@ -347,7 +347,7 @@ the GitHub PR:
347
347
348
348
If your PR is ready for review, select ``Create pull request ``. Otherwise,
349
349
select ``Create draft pull request `` and mark it as ready for review once
350
- you it includes all of your changes and you are satisfied with it.
350
+ it includes all of your changes and you are satisfied with it.
351
351
352
352
If you need to change a PR title, to its right, click the ``Edit `` button,
353
353
which becomes a ``Save `` button while you are in editing mode.
0 commit comments