From 27ba64787805643264e66d3c7496ed5c24371b3e Mon Sep 17 00:00:00 2001 From: DhruvSondhi Date: Thu, 20 May 2021 21:27:35 +0530 Subject: [PATCH] Fixing some more changes --- docs/development/continuous_integration.rst | 2 +- docs/development/git_workflow.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/development/continuous_integration.rst b/docs/development/continuous_integration.rst index 8679b344670..c71c0feef4a 100644 --- a/docs/development/continuous_integration.rst +++ b/docs/development/continuous_integration.rst @@ -15,7 +15,7 @@ Azure Repos ----------- Azure Repos is just another service to store Git repositories. -Currently, we use Azure Repos to mirror `tardis-refdata` +Currently, we use Azure Repos to mirror ``tardis-refdata`` repository since Azure does not impose limits on LFS bandwith nor storage. diff --git a/docs/development/git_workflow.rst b/docs/development/git_workflow.rst index d848bb34580..7ff68e0c33b 100644 --- a/docs/development/git_workflow.rst +++ b/docs/development/git_workflow.rst @@ -246,7 +246,7 @@ or ``buxfix-for-issue-42``. Generally, you will want to keep your feature branches on your public GitHub_ fork. To do this, you `git push`_ this new branch up to your GitHub repo. Generally (if you followed the instructions in these pages, and -by default), git will have a link to your GitHub repo, called `origin`. You +by default), git will have a link to your GitHub repo, called ``origin``. You push up to your own repo on GitHub with:: git push origin my-new-feature