Switch order of GitHub and Observable deploys

Author: dkrasne

.github/workflows/deploy.yml

@@ -48,15 +48,15 @@ jobs:
           git push
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      - name: Deploy to Observable Cloud
-        run: npm run deploy -- --message "$(git log -1 --pretty=%s)"
-        env:
-          OBSERVABLE_TOKEN: ${{ secrets.OBSERVABLE_DEPLOY_TOKEN }}
       - uses: actions/configure-pages@v4
-
       - uses: actions/upload-pages-artifact@v3
         with:
           path: dist
       - name: Deploy to GitHub Pages
         id: deployment
-        uses: actions/deploy-pages@v4
+        uses: actions/deploy-pages@v4
+        
+      - name: Deploy to Observable Cloud
+        run: npm run deploy -- --message "$(git log -1 --pretty=%s)"
+        env:
+          OBSERVABLE_TOKEN: ${{ secrets.OBSERVABLE_DEPLOY_TOKEN }}

src/about.md

@@ -94,7 +94,7 @@ The critical core tables are `word instance`, `word-level intertext`, `word-leve
 
 While the project overall is strictly concerned with Latin poetry, Greek texts also need to be included within the database due to Latin poetry’s clear intertextual engagement with them. Accordingly, each author has a language property that specifies them as either a Greek or Latin author. While this does not allow for the possibility of bilingual authors, our surviving texts do not really compass this scenario, or do so insufficiently to justify putting the language label with works instead of authors. ([The Late Antique poet Claudian is one such counterexample](https://antigonejournal.com/2024/12/claudians-gigantomachia/), but he is so late that his works are unlikely to serve as the *source* of any intertexts in the database; and this is the only situation in which a Greek text can enter the database.) Prose texts are also included in the database, but they, like Greek authors, cannot be selected in the interface.
 
-Finally, each `word-level intertext` records at least one scholarly source for its data (sometimes the original publication proposing the intertext, and sometimes a commentary), sources that are collectively stored in a `publication` table. (It is also possible to record an ancient work as the scholarly source, since occasionally the explicit recognition of an intertext goes back to a grammarian of antiquity.) This information is made available when a passage is selected.
+Finally, each `word-level intertext` records at least one scholarly source for its data (sometimes the original publication proposing the intertext, sometimes a later publication, and sometimes a commentary), sources that are collectively stored in a `publication` table. (It is also possible to record an ancient work as the scholarly source, since occasionally the explicit recognition of an intertext goes back to a grammarian of antiquity.) This information is made available when a passage is selected.
 
 In addition to the tables described above, the two tables `authorship problem` and `collection` are used to model less straightforward forms of authorship (such as anonymity, uncertain authorship, or preservation in a collection of works), while the three tables `textual problem`, `alternate reading`, and `word-level intertext modification` are newer additions to the database that are used to model variant readings and the changes they imply for proposed intertextual allusions. Some additional information about particulars of the database and project can be found on the [Frequently Asked Questions page](./faq).
 

src/index.md

@@ -1190,9 +1190,9 @@ for (let i in sourcesFilteredIDs) {
 	// modern sources
 	else {
 	// add author(s), separated by comma if more than one
-	for (let i in pub.authorIDs) {
-		pubString += i > 0 ? ', ' : '';
-		let author = lookupIDTable.get(pub.authorIDs[i]);
+	for (let j in pub.authorIDs) {
+		pubString += j > 0 ? ', ' : '';
+		let author = lookupIDTable.get(pub.authorIDs[j]);
 		pubString += author;
 	}