More context for BitBucket archive in docs, mailing list link, regular apostrophes

rpanderson · rpanderson · commit c0553848397c · 2020-05-28T22:20:57.000+10:00
diff --git a/README.md b/README.md
@@ -59,7 +59,7 @@ Upon migrating the code base to GitHub and publishing distributions on PyPI in A
 
 ### Profile directories
 
-The _labscript suite_ profile directory, containing application configurations, logs, and user-side code, is now located by default in the current user’s home directory, e.g. for a local user named `wkheisenberg` this is:
+The _labscript suite_ profile directory, containing application configurations, logs, and user-side code, is now located by default in the current user's home directory, e.g. for a local user named `wkheisenberg` this is:
 
 * `C:\Users\wkheisenberg\labscript-suite` on Windows.
 * `~/labscript-suite` or `/home/wkheisenberg/labscript-suite` on Linux and Mac OS X.
@@ -190,13 +190,13 @@ We are very grateful for all the contributions users have made in the past decad
 
 The issue tracking on GitHub is very similar to BitBucket, with the added advantage that you can add inter-repository issue references, e.g. referring to [labscript-suite/runmanager#68](https://github.com/labscript-suite/runmanager/issues/68) in any issue or pull request will link to the corresponding issue. We have imported all issues from the BitBucket repositories into the GitHub repositories. This import is not perfect (as each comment is now posted by Phil Starkey) but the comments have been modified to contain the original author attribution. We have also updated all links to files, pull requests, issues, and commits so that they point to the equivalent GitHub location and/or the archived copy of the data (as discussed above).
 
-Please use the GitHub issue tracker (rather than the mailing list) for:
+Please use the issue tracker of the relevant GitHub repository for:
 
-* Reporting **bugs** (when something doesn’t work or works ina way you didn’t expect);
+* Reporting **bugs** (when something doesn't work or works in a way you didn't expect);
 * Suggesting **enhancements**: new features or requests;
 * Issues relating to **installation**, **performance**, or **documentation**.
 
-However, advice for how to do something with the existing functionality of the _labscript suite_ is better suited to the mailing list.
+For advice on _how_ to use the existing functionality of the _labscript suite_, please use our [mailing list](http://groups.google.com/group/labscriptsuite).
 
 
 ### Request for developers
diff --git a/docs/source/archive.md b/docs/source/archive.md
@@ -1,6 +1,6 @@
 ## BitBucket archive
 
-Some repository metadata (such as pull request discussions) could not be migrated directly from BitBucket to GitHub. As such, we have created an archived copy of everything that was on BitBucket. This includes:
+In April–May 2020 the _labscript suite_ code base was migrated from BitBucket to GitHub. All commit history and issues was preserved, however some repository metadata (such as pull request discussions) could not be migrated directly. As such, we have created an archived copy of everything that was on BitBucket. This includes:
 
 * Issues (as they appear on BitBucket);
 * Pull requests discussions;
diff --git a/docs/source/contributing.md b/docs/source/contributing.md
@@ -7,13 +7,13 @@ We are very grateful for all the contributions users have made in the past decad
 
 The issue tracking on GitHub is very similar to BitBucket, with the added advantage that you can add inter-repository issue references, e.g. referring to [labscript-suite/runmanager#68](https://github.com/labscript-suite/runmanager/issues/68) in any issue or pull request will link to the corresponding issue. We have imported all issues from the BitBucket repositories into the GitHub repositories. This import is not perfect (as each comment is now posted by Phil Starkey) but the comments have been modified to contain the original author attribution. We have also updated all links to files, pull requests, issues, and commits so that they point to the equivalent GitHub location and/or the archived copy of the data (as discussed above).
 
-Please use the GitHub issue tracker (rather than the mailing list) for:
+Please use the issue tracker of the relevant GitHub repository for:
 
-* Reporting **bugs** (when something doesn’t work or works ina way you didn’t expect);
+* Reporting **bugs** (when something doesn't work or works in a way you didn't expect);
 * Suggesting **enhancements**: new features or requests;
 * Issues relating to **installation**, **performance**, or **documentation**.
 
-However, advice for how to do something with the existing functionality of the _labscript suite_ is better suited to the mailing list.
+For advice on _how_ to use the existing functionality of the _labscript suite_, please use our [mailing list](http://groups.google.com/group/labscriptsuite).
 
 
 ### Request for developers
@@ -46,7 +46,7 @@ You can learn more about this branching model at:
 
 ### Learning Git
 
-As our former development, installation, and upgrading practices involved Mercurial revision-control, some of you may not be familiar with Git. While you no longer need to use _any_ revision control system to use the _labscript suite_, those of you wanting to contribute to development who aren’t acquainted with Git may benefit from these resources:
+As our former development, installation, and upgrading practices involved Mercurial revision-control, some of you may not be familiar with Git. While you no longer need to use _any_ revision control system to use the _labscript suite_, those of you wanting to contribute to development who aren't acquainted with Git may benefit from these resources:
 
 * NumPy: [Getting started with Git development](https://numpy.org/doc/stable/dev/gitwash/development_setup.html)
 * [GitHub Guides](https://guides.github.com/): Very cogent information for beginners. We recommend starting with:
diff --git a/docs/source/installation.md b/docs/source/installation.md
@@ -10,7 +10,7 @@ This makes it far easier to get started using the _labscript suite_, as you no l
 
 ### Virtual environments
 
-We recommend installing labscript (regular or developer mode) in a [virtual environment](https://packaging.python.org/tutorials/installing-packages/#creating-virtual-environments). This helps sandbox the codebase without interfering with (or being interfered with) your system Python installation, or Python environments used for other purposes. There are a number of ways to configure a virtual environment. If you are unfamiliar with doing so, we recommend using the [venv module](https://docs.python.org/3/library/venv.html), part of the Python Standard Library. Here’s an example (on Windows):
+We recommend installing labscript (regular or developer mode) in a [virtual environment](https://packaging.python.org/tutorials/installing-packages/#creating-virtual-environments). This helps sandbox the codebase without interfering with (or being interfered with) your system Python installation, or Python environments used for other purposes. There are a number of ways to configure a virtual environment. If you are unfamiliar with doing so, we recommend using the [venv module](https://docs.python.org/3/library/venv.html), part of the Python Standard Library. Here's an example (on Windows):
 
 
 #### Quick start
@@ -46,7 +46,7 @@ Once activated, the name of the virtual environment (in this case, `.venv`) will
     C:\labscript-suite> .venv\Scripts\activate
     ```
 
-    _Note:_ This step is OS specific, e.g. on Linux it’s `source .venv/bin/activate`.
+    _Note:_ This step is OS specific, e.g. on Linux it's `source .venv/bin/activate`.
 
 4. Update the Python package installer and other installation packages of your virtual environment.
 
@@ -74,7 +74,7 @@ C:\labscript-suite> .venv\Scripts\activate
 
 #### Detailed instructions
 
-1. Activate the virtual environment (this step is OS specific, e.g. on Linux it’s `source .venv/bin/activate`).
+1. Activate the virtual environment (this step is OS specific, e.g. on Linux it's `source .venv/bin/activate`).
 
     ```
     C:\labscript-suite> .venv\Scripts\activate
