From 5d1a71aaa81e66ed7de49f2aeb52074d47cb0c98 Mon Sep 17 00:00:00 2001 From: HopefulHope Date: Mon, 29 Jun 2026 15:22:31 -0400 Subject: [PATCH 1/2] fixed issue 306 of incorrect capitalizations in index --- .cache/.web_assets.json | 1 + source/sec_community_communication.ptx | 2 +- source/sec_dev_shell.ptx | 2 +- source/sec_docu_scope.ptx | 2 +- source/sec_git_getting_started.ptx | 6 +++--- source/sec_git_github.ptx | 4 ++-- 6 files changed, 9 insertions(+), 8 deletions(-) create mode 100644 .cache/.web_assets.json diff --git a/.cache/.web_assets.json b/.cache/.web_assets.json new file mode 100644 index 00000000..c86e2d61 --- /dev/null +++ b/.cache/.web_assets.json @@ -0,0 +1 @@ +{"qrcode": "b4b221239273bf17a1895e898c978c49b6b71f082bd9ba7758117db86012989d"} \ No newline at end of file diff --git a/source/sec_community_communication.ptx b/source/sec_community_communication.ptx index e554e88f..04a7f288 100644 --- a/source/sec_community_communication.ptx +++ b/source/sec_community_communication.ptx @@ -222,7 +222,7 @@ Wiki - Wikis + wikis

Simply stated, a wiki is a hypertext publication where the pages are a user-editable, easy-to-use, asynchronous way of putting semi-permanent content on the web. diff --git a/source/sec_dev_shell.ptx b/source/sec_dev_shell.ptx index 4b6ba195..527fac13 100644 --- a/source/sec_dev_shell.ptx +++ b/source/sec_dev_shell.ptx @@ -49,7 +49,7 @@

  • What is a <term>Command Line Interface (CLI)</term>?

    - Command Line Interface + command line interface CLI A CLI refers to any interface that works with text-based commands and text-based output. We will be using a shell, which is an example of a CLI.

    diff --git a/source/sec_docu_scope.ptx b/source/sec_docu_scope.ptx index 8bd3be2b..a9067946 100644 --- a/source/sec_docu_scope.ptx +++ b/source/sec_docu_scope.ptx @@ -90,7 +90,7 @@
  • CHANGELOG

    - CHANGELOG + changelog Documenting changes to the project over time, the CHANGELOG usually includes a list of all releases and a summary of the changes that were made in each one.

    diff --git a/source/sec_git_getting_started.ptx b/source/sec_git_getting_started.ptx index 9701708a..e8c31f6e 100644 --- a/source/sec_git_getting_started.ptx +++ b/source/sec_git_getting_started.ptx @@ -43,7 +43,7 @@

    - Local VCS + local VCS To deal with this issue, programmers long ago developed a more formal system of version control. Local VCSs provide a more automatic, less error-prone and more structured way of keeping all the changes to files under revision control on the local computer. Local VCSs typically operate quickly because they do not have to communicate with a remote server. With a local system, developers have access to the entire history of the codebase on their local machine, and they can work on the codebase offline, without an internet connection.

    @@ -61,7 +61,7 @@

    - Centralized VCS + centralized VCS Many developers need to collaborate with other developers on other systems. To deal with this, centralized VCSs were developed. These systems (such as CVS, Subversion, and Perforce) have a single server that contains all the versioned files, and a number of clients check out files from that central server. For many years, this was the standard for version control.

    @@ -85,7 +85,7 @@

    - Distributed VCS + distributed VCS This is where distributed VCSs step in. In a distributed VCS (such as Git, Mercurial, Bazaar or Darcs), clients don’t just check out the latest snapshot of the files; rather, they fully mirror the repository, including its full history. Thus, if any server dies, and these systems were collaborating via that server, any of the client repositories can be copied back up to the server to restore it. Every clone is really a full backup of all the data.

    diff --git a/source/sec_git_github.ptx b/source/sec_git_github.ptx index 9fb58c3d..cb548014 100644 --- a/source/sec_git_github.ptx +++ b/source/sec_git_github.ptx @@ -40,7 +40,7 @@

    - Fork + fork If you want to contribute to an existing project to which you don’t have write access (aka push access), you can fork the project. When you “fork” a project, GitHub will make a copy of the project that is entirely yours; it lives in your namespace, and you can push to it.

    @@ -807,7 +807,7 @@ How big are these slings and in particular, these arrows?

    - README + readme The README file explains your project, what it does, why it is useful, etc. If GitHub detects a README file in your source, it will render it on the landing page of the project, so this file is often the first item a visitor will see when visiting your repository. From ff5a337e259c4fd9bd6c4faf5d9e2794e7f280d0 Mon Sep 17 00:00:00 2001 From: Jan Pearce Date: Fri, 24 Jul 2026 09:36:15 -0400 Subject: [PATCH 2/2] remove asset from .cache --- .cache/.web_assets.json | 1 - 1 file changed, 1 deletion(-) delete mode 100644 .cache/.web_assets.json diff --git a/.cache/.web_assets.json b/.cache/.web_assets.json deleted file mode 100644 index c86e2d61..00000000 --- a/.cache/.web_assets.json +++ /dev/null @@ -1 +0,0 @@ -{"qrcode": "b4b221239273bf17a1895e898c978c49b6b71f082bd9ba7758117db86012989d"} \ No newline at end of file