ACDguide / BigData

Working with big/challenging data collections
https://ACDguide.github.io/BigData
Other
5 stars 5 forks source link

fix typos in software-other.md #73

Closed Thomas-Moore-Creative closed 1 year ago

Thomas-Moore-Creative commented 1 year ago

fix typos (and GitNoob testing PR to patched branch from fork)

Thomas-Moore-Creative commented 1 year ago

I'm going to merge this trivial PR which should make changes to @paolap 's ACDguide:restructure_paola branch?

paolap commented 1 year ago

go for it, I might have fixed one typo myself in the meantime and added a bit more content, but that should make the experiment more interesting

Thomas-Moore-Creative commented 1 year ago

[ confused face ] I think I've pulled down the patched branch and built the book but I'm confused as it seems the file naming structure had / has changed and I'm not clear if my trivial typo changes are there as I now see that content locally in a different file name file:///......./code/BigData/BigData/_build/html/tools/tools-other.html with the typos still there.

I'll try to have a further play when I can.

paolap commented 1 year ago

Just clean up your build completely "rm -rf _build" and build again. I changed the names probably after you forked and your changes have been merged with mine, so added to the renamed files. The "tools" files are a relic, they shouldn't show in the new build. The changes should be in the software files. You can see the order here, I renamed the files just before you made the commit: https://github.com/ACDguide/BigData/compare/main...restructure_paola

Thomas-Moore-Creative commented 1 year ago

I'm just a huge GitNoob and failed to remember that my local repo is a fork of ACDguide:restructure_paola and (DUH!) I need to sync my fork before pulling down will bring my local copy the changes!!

Seems like I've advanced to being able to fix typos in a patched branch of a fork. Changes rendered.