You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucenenet.apache.org by pa...@apache.org on 2026/06/11 18:57:37 UTC
(lucenenet) branch master updated: misc: fix grammar and spelling (#1335)
This is an automated email from the ASF dual-hosted git repository.
paulirwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/lucenenet.git
The following commit(s) were added to refs/heads/master by this push:
new 27ee39c04 misc: fix grammar and spelling (#1335)
27ee39c04 is described below
commit 27ee39c0478102fcf94b7e055f296d6920dee920
Author: John Bampton <jb...@users.noreply.github.com>
AuthorDate: Fri Jun 12 04:57:30 2026 +1000
misc: fix grammar and spelling (#1335)
---
.../publish-test-results-for-test-projects.yml | 2 +-
.build/psake/public/Include.ps1 | 6 +++---
.build/runbuild.ps1 | 2 +-
build | 2 +-
build.bat | 2 +-
src/Lucene.Net.Analysis.Common/Collation/package.md | 2 +-
src/Lucene.Net.Analysis.ICU/overview.md | 2 +-
src/Lucene.Net/Document/package.md | 2 +-
src/Lucene.Net/Search/Similarities/package.md | 2 +-
src/Lucene.Net/Search/package.md | 2 +-
src/dotnet/tools/lucene-cli/docs/index/merge.md | 2 +-
websites/apidocs/apiSpec/core/Lucene_Net_Codecs.md | 8 ++++----
websites/site/contributing/community-links.md | 2 +-
websites/site/contributing/documentation.md | 14 +++++++-------
websites/site/contributing/make-release.md | 2 +-
websites/site/contributing/source.md | 2 +-
websites/site/contributing/versioning.md | 2 +-
websites/site/release-notes/version-4.8.0-beta00016.md | 2 +-
18 files changed, 29 insertions(+), 29 deletions(-)
diff --git a/.build/azure-templates/publish-test-results-for-test-projects.yml b/.build/azure-templates/publish-test-results-for-test-projects.yml
index c164fb723..3fb603eb6 100644
--- a/.build/azure-templates/publish-test-results-for-test-projects.yml
+++ b/.build/azure-templates/publish-test-results-for-test-projects.yml
@@ -17,7 +17,7 @@
# Runs Publish Test Results task for all Lucene.Net test projects
-# The tasks can be easily re-generated (except for any special cases) using the following powershell script
+# The tasks can be easily re-generated (except for any special cases) using the following PowerShell script
#$source_directory = "F:/Projects/lucenenet" # Change to your repo location
#
diff --git a/.build/psake/public/Include.ps1 b/.build/psake/public/Include.ps1
index 3c163fe03..61d050634 100644
--- a/.build/psake/public/Include.ps1
+++ b/.build/psake/public/Include.ps1
@@ -1,14 +1,14 @@
function Include {
<#
.SYNOPSIS
- Include the functions or code of another powershell script file into the current build script's scope
+ Include the functions or code of another PowerShell script file into the current build script's scope
.DESCRIPTION
- A build script may declare an "includes" function which allows you to define a file containing powershell code to be included
+ A build script may declare an "includes" function which allows you to define a file containing PowerShell code to be included
and added to the scope of the currently running build script. Code from such file will be executed after code from build script.
.PARAMETER fileNamePathToInclude
- A string containing the path and name of the powershell file to include
+ A string containing the path and name of the PowerShell file to include
.EXAMPLE
A sample build script is shown below:
diff --git a/.build/runbuild.ps1 b/.build/runbuild.ps1
index e22b2a4f8..deaf10f41 100644
--- a/.build/runbuild.ps1
+++ b/.build/runbuild.ps1
@@ -106,7 +106,7 @@ task Init -depends CheckSDK, UpdateLocalSDKVersion -description "This task makes
Write-Host "Configuration: $configuration"
Write-Host "Platform: $platform"
Write-Host "MaximumParallelJobs: $($maximumParallelJobs.ToString())"
- Write-Host "Powershell Version: $($PSVersionTable.PSVersion)"
+ Write-Host "PowerShell Version: $($PSVersionTable.PSVersion)"
Ensure-Directory-Exists "$artifactsDirectory"
Ensure-Directory-Exists "$nugetPackageDirectory" # helpful when adding this path to your nuget sources for local installs
diff --git a/build b/build
index 7ae6023ff..252808d06 100755
--- a/build
+++ b/build
@@ -49,7 +49,7 @@
# -----------------------------------------------------------------------------------
if ! command -v pwsh &> /dev/null
then
- echo "Powershell Core could not be found. Please install version 3 or higher."
+ echo "PowerShell Core could not be found. Please install version 3 or higher."
exit
fi
pwsh -ExecutionPolicy bypass -Command "& './build.ps1'" "$@"
diff --git a/build.bat b/build.bat
index 707f6d508..2165a2f5e 100644
--- a/build.bat
+++ b/build.bat
@@ -50,4 +50,4 @@ GOTO endcommentblock
:: -----------------------------------------------------------------------------------
:endcommentblock
where pwsh >nul 2>nul
-if %ERRORLEVEL% NEQ 0 (echo "Powershell could not be found. Please install version 3 or higher.") else (pwsh -ExecutionPolicy bypass -Command "& '%~dpn0.ps1'" %*)
+if %ERRORLEVEL% NEQ 0 (echo "PowerShell could not be found. Please install version 3 or higher.") else (pwsh -ExecutionPolicy bypass -Command "& '%~dpn0.ps1'" %*)
diff --git a/src/Lucene.Net.Analysis.Common/Collation/package.md b/src/Lucene.Net.Analysis.Common/Collation/package.md
index 314f6ea59..a6c8070e1 100644
--- a/src/Lucene.Net.Analysis.Common/Collation/package.md
+++ b/src/Lucene.Net.Analysis.Common/Collation/package.md
@@ -109,4 +109,4 @@ summary: *content
`ICUCollationKeyAnalyzer`, available in the [icu analysis module]({@docRoot}/../analyzers-icu/overview-summary.html), uses ICU4J's `Collator`, which makes its version available, thus allowing collation to be versioned independently from the JVM. `ICUCollationKeyAnalyzer` is also significantly faster and generates significantly shorter keys than `CollationKeyAnalyzer`. See [http://site.icu-project.org/charts/collation-icu4j-sun](http://site.icu-project.org/charts/collation-icu4j-sun) for [...]
- `CollationKey`s generated by `java.text.Collator`s are not compatible with those those generated by ICU Collators. Specifically, if you use `CollationKeyAnalyzer` to generate index terms, do not use `ICUCollationKeyAnalyzer` on the query side, or vice versa.
\ No newline at end of file
+ `CollationKey`s generated by `java.text.Collator`s are not compatible with those generated by ICU Collators. Specifically, if you use `CollationKeyAnalyzer` to generate index terms, do not use `ICUCollationKeyAnalyzer` on the query side, or vice versa.
\ No newline at end of file
diff --git a/src/Lucene.Net.Analysis.ICU/overview.md b/src/Lucene.Net.Analysis.ICU/overview.md
index 89046207e..a7fdbc15d 100644
--- a/src/Lucene.Net.Analysis.ICU/overview.md
+++ b/src/Lucene.Net.Analysis.ICU/overview.md
@@ -193,7 +193,7 @@ Assert.AreEqual(1, result.Length, "The index Term should be included.");
`ICUCollationKeyAnalyzer` uses ICU4N's `Collator`, which makes its version available, thus allowing collation to be versioned independently from the .NET target framework. `ICUCollationKeyAnalyzer` is also fast.
- `SortKey`s generated by `CompareInfo`s are not compatible with those those generated by ICU Collators. Specifically, if you use `CollationKeyAnalyzer` to generate index terms, do not use `ICUCollationKeyAnalyzer` on the query side, or vice versa.
+ `SortKey`s generated by `CompareInfo`s are not compatible with those generated by ICU Collators. Specifically, if you use `CollationKeyAnalyzer` to generate index terms, do not use `ICUCollationKeyAnalyzer` on the query side, or vice versa.
* * *
diff --git a/src/Lucene.Net/Document/package.md b/src/Lucene.Net/Document/package.md
index 9f5e036b1..7e5a1d352 100644
--- a/src/Lucene.Net/Document/package.md
+++ b/src/Lucene.Net/Document/package.md
@@ -34,4 +34,4 @@ Note: it is common to refer to <xref:Lucene.Net.Documents.Document>s having <xre
First and foremost, a <xref:Lucene.Net.Documents.Document> is something created by the user application. It is your job to create Documents based on the content of the files you are working with in your application (Word, txt, PDF, Excel or any other format.) How this is done is completely up to you. That being said, there are many tools available in other projects that can make the process of taking a file and converting it into a Lucene <xref:Lucene.Net.Documents.Document>.
-The <xref:Lucene.Net.Documents.DateTools> is a utility class to make dates and times searchable (remember, Lucene only searches text). <xref:Lucene.Net.Documents.Int32Field>, <xref:Lucene.Net.Documents.Int64Field>, <xref:Lucene.Net.Documents.SingleField> and <xref:Lucene.Net.Documents.DoubleField> are a special helper class to simplify indexing of numeric values (and also dates) for fast range range queries with <xref:Lucene.Net.Search.NumericRangeQuery> (using a special sortable string [...]
\ No newline at end of file
+The <xref:Lucene.Net.Documents.DateTools> is a utility class to make dates and times searchable (remember, Lucene only searches text). <xref:Lucene.Net.Documents.Int32Field>, <xref:Lucene.Net.Documents.Int64Field>, <xref:Lucene.Net.Documents.SingleField> and <xref:Lucene.Net.Documents.DoubleField> are a special helper class to simplify indexing of numeric values (and also dates) for fast range queries with <xref:Lucene.Net.Search.NumericRangeQuery> (using a special sortable string repres [...]
\ No newline at end of file
diff --git a/src/Lucene.Net/Search/Similarities/package.md b/src/Lucene.Net/Search/Similarities/package.md
index 63d88a7dc..8ada04cad 100644
--- a/src/Lucene.Net/Search/Similarities/package.md
+++ b/src/Lucene.Net/Search/Similarities/package.md
@@ -71,4 +71,4 @@ If you are interested in use cases for changing your similarity, see the Lucene
In general, Chris Hostetter sums it up best in saying (from [the Lucene users's mailing list](http://www.gossamer-threads.com/lists/lucene/java-user/39125#39125)):
-> [One would override the Similarity in] ... any situation where you know more about your data then just that it's "text" is a situation where it *might* make sense to to override your Similarity method.
\ No newline at end of file
+> [One would override the Similarity in] ... any situation where you know more about your data then just that it's "text" is a situation where it *might* make sense to override your Similarity method.
\ No newline at end of file
diff --git a/src/Lucene.Net/Search/package.md b/src/Lucene.Net/Search/package.md
index 620befab1..3cf1d1ca4 100644
--- a/src/Lucene.Net/Search/package.md
+++ b/src/Lucene.Net/Search/package.md
@@ -162,7 +162,7 @@ The [Weight](xref:Lucene.Net.Search.Weight) interface provides an internal repre
2. [GetValueForNormalization()](xref:Lucene.Net.Search.Weight#Lucene_Net_Search_Weight_GetValueForNormalization) — A weight can return a floating point value to indicate its magnitude for query normalization. Typically a weight such as TermWeight that scores via a [Similarity](xref:Lucene.Net.Search.Similarities.Similarity) will just defer to the Similarity's implementation: [SimWeight.GetValueForNormalization()](xref:Lucene.Net.Search.Similarities.Similarity.SimWeight#Lucene_Net_Search_ [...]
3. [Normalize(float norm, float topLevelBoost)](xref:Lucene.Net.Search.Weight#Lucene_Net_Search_Weight_Normalize_System_Single_System_Single_) — Performs query normalization:
* `topLevelBoost`: A query-boost factor from any wrapping queries that should be multiplied into every document's score. For example, a TermQuery that is wrapped within a BooleanQuery with a boost of `5` would receive this value at this time. This allows the TermQuery (the leaf node in this case) to compute this up-front a single time (e.g. by multiplying into the IDF), rather than for every document.
- * `norm`: Passes in a a normalization factor which may allow for comparing scores between queries. Typically a weight such as TermWeight that scores via a [Similarity](xref:Lucene.Net.Search.Similarities.Similarity) will just defer to the Similarity's implementation: [SimWeight.Normalize(float, float)](xref:Lucene.Net.Search.Similarities.Similarity.SimWeight#Lucene_Net_Search_Similarities_Similarity_SimWeight_Normalize_System_Single_System_Single_).
+ * `norm`: Passes in a normalization factor which may allow for comparing scores between queries. Typically a weight such as TermWeight that scores via a [Similarity](xref:Lucene.Net.Search.Similarities.Similarity) will just defer to the Similarity's implementation: [SimWeight.Normalize(float, float)](xref:Lucene.Net.Search.Similarities.Similarity.SimWeight#Lucene_Net_Search_Similarities_Similarity_SimWeight_Normalize_System_Single_System_Single_).
4. [GetScorer(AtomicReaderContext context, IBits acceptDocs)](xref:Lucene.Net.Search.Weight#Lucene_Net_Search_Weight_GetScorer_Lucene_Net_Index_AtomicReaderContext_Lucene_Net_Util_IBits_) — Construct a new [Scorer](xref:Lucene.Net.Search.Scorer) for this Weight. See [The Scorer Class](#the-scorer-class) below for help defining a Scorer. As the name implies, the Scorer is responsible for doing the actual scoring of documents given the Query.
5. [GetScorer(AtomicReaderContext, bool scoreDocsInOrder, IBits acceptDocs)](xref:Lucene.Net.Search.Weight#Lucene_Net_Search_Weight_GetBulkScorer_Lucene_Net_Index_AtomicReaderContext_System_Boolean_Lucene_Net_Util_IBits_) — Construct a new [BulkScorer](xref:Lucene.Net.Search.BulkScorer) for this Weight. See [The BulkScorer Class](#the-bulkscorer-class) below for help defining a BulkScorer. This is an optional method, and most queries do not implement it.
6. [Explain(AtomicReaderContext context, int doc)](xref:Lucene.Net.Search.Weight#Lucene_Net_Search_Weight_Explain_Lucene_Net_Index_AtomicReaderContext_System_Int32_) — Provide a means for explaining why a given document was scored the way it was. Typically a weight such as TermWeight that scores via a [Similarity](xref:Lucene.Net.Search.Similarities.Similarity) will make use of the Similarity's implementation: [SimScorer.Explain(int doc, Explanation freq)](xref:Lucene.Net.Search.Similari [...]
diff --git a/src/dotnet/tools/lucene-cli/docs/index/merge.md b/src/dotnet/tools/lucene-cli/docs/index/merge.md
index b492d8fb4..2bca0bb02 100644
--- a/src/dotnet/tools/lucene-cli/docs/index/merge.md
+++ b/src/dotnet/tools/lucene-cli/docs/index/merge.md
@@ -12,7 +12,7 @@ lucene index merge <OUTPUT_DIRECTORY> <INPUT_DIRECTORY> <INPUT_DIRECTORY_2>[ <IN
### Description
-Merges the the input index directories into a combined index at the output directory path.
+Merges the input index directories into a combined index at the output directory path.
### Arguments
diff --git a/websites/apidocs/apiSpec/core/Lucene_Net_Codecs.md b/websites/apidocs/apiSpec/core/Lucene_Net_Codecs.md
index a344f3bbc..45480ece5 100644
--- a/websites/apidocs/apiSpec/core/Lucene_Net_Codecs.md
+++ b/websites/apidocs/apiSpec/core/Lucene_Net_Codecs.md
@@ -145,7 +145,7 @@ public class MyPostingsFormat : PostingsFormat
}
```
-Extend the the default <xref:Lucene.Net.Codecs.Lucene46.Lucene46Codec>, and override [GetPostingsFormatForField(string)](xref:Lucene.Net.Codecs.Lucene46.Lucene46Codec) to return your custom postings format.
+Extend the default <xref:Lucene.Net.Codecs.Lucene46.Lucene46Codec>, and override [GetPostingsFormatForField(string)](xref:Lucene.Net.Codecs.Lucene46.Lucene46Codec) to return your custom postings format.
```cs
[CodecName("MyCodec")]
@@ -295,7 +295,7 @@ The above block will register a new codec named `MyCodec` with the test framewor
Set an environment variable named `lucene:tests:codec` to the name of the codec.
```
-$env:lucene:tests:codec = "MyCodec"; # Powershell example
+$env:lucene:tests:codec = "MyCodec"; # PowerShell example
```
#### Setting the Default Codec using a Configuration File
@@ -319,8 +319,8 @@ Similarly to codecs, the default postings format or doc values format can be set
Set environment variables named `lucene:tests:postingsformat` to the name of the postings format and/or `lucene:tests:docvaluesformat` to the name of the doc values format.
```
-$env:lucene:tests:postingsformat = "MyPostingsFormat"; # Powershell example
-$env:lucene:tests:docvaluesformat = "MyDocValuesFormat"; # Powershell example
+$env:lucene:tests:postingsformat = "MyPostingsFormat"; # PowerShell example
+$env:lucene:tests:docvaluesformat = "MyDocValuesFormat"; # PowerShell example
```
#### Configuration File
diff --git a/websites/site/contributing/community-links.md b/websites/site/contributing/community-links.md
index db3d74c7d..152f38975 100644
--- a/websites/site/contributing/community-links.md
+++ b/websites/site/contributing/community-links.md
@@ -47,7 +47,7 @@ https://blog.beckshome.com/). Source for all projects [available on GitHub](http
- [Lazily setting the SetMultiTermRewriteMethod](https://shazwazza.com/post/how-to-set-rewrite-method-on-queries-lazily-in-lucene/)
- How-to guide on lazily setting the rewrite method of the query parser instead of eagerly since you may not know it is required until the query is built.
- [Spatial Search with Lucene.Net and Examine](https://shazwazza.com/post/spatial-search-with-examine-and-lucene/)
- - How-to guide on implementing geo spatial search with Lucene.Net in the context of using [Examine](https://github.com/shazwazza/examine) to manage Lucene.Net.
+ - How-to guide on implementing geospatial search with Lucene.Net in the context of using [Examine](https://github.com/shazwazza/examine) to manage Lucene.Net.
- [Implementing Search in Blazor WebAssembly with Lucene.Net](https://www.aaron-powell.com/posts/2019-11-29-implementing-search-in-blazor-webassembly-with-lucenenet/)
- How-to guide on setting up Lucene.Net to work with [Blazor WebAssembly](https://docs.microsoft.com/en-gb/aspnet/core/blazor/?view=aspnetcore-3.0&WT.mc_id=aaronpowell-blog-aapowell#blazor-webassembly).
diff --git a/websites/site/contributing/documentation.md b/websites/site/contributing/documentation.md
index ea1caaf72..2a800d54a 100644
--- a/websites/site/contributing/documentation.md
+++ b/websites/site/contributing/documentation.md
@@ -12,13 +12,13 @@ _Details about this website and the API documentation site and how to help contr
The website and the api documentation source code is found in the same Git repository as the Lucene.Net code in the folder: `./websites/`. The website and documentation site is built with a static site generator called [DocFx](https://dotnet.github.io/docfx/) and all of the content/pages are created using Markdown files.
-To submit changes for the website, create a Pull Request to the [Lucene Git repositoriy](https://github.com/apache/lucenenet). (See [Contributing](xref:contributing#submit-a-pull-request) for details)
+To submit changes for the website, create a Pull Request to the [Lucene Git repository](https://github.com/apache/lucenenet). (See [Contributing](xref:contributing#submit-a-pull-request) for details)
## Website
### Build script
-To build the website and run it on your machine, run the Powershell script: `./websites/site/site.ps1` with the `-ServeDocs` flag. For example:
+To build the website and run it on your machine, run the PowerShell script: `./websites/site/site.ps1` with the `-ServeDocs` flag. For example:
```
./websites/site/site.ps1 -ServeDocs
@@ -62,7 +62,7 @@ The file/folder structure is within `./websites/site`:
### Build script
-To build the api docs and run it on your machine, run the Powershell script: `./websites/apidocs/docs.ps1`. For example:
+To build the api docs and run it on your machine, run the PowerShell script: `./websites/apidocs/docs.ps1`. For example:
```
./websites/apidocs/docs.ps1 -ServeDocs -LuceneNetVersion 4.8.0-beta00008 -BaseUrl http://localhost:8080
@@ -95,9 +95,9 @@ The file/folder structure is within `./websites/apidocs`:
- `docs.ps1` - The build script
- `docfx.*.json` - The DocFx configuration files _(see docfx manual for further info)_
- - `docfx.{library}.json` - Where {library} is an individual Lucene.NET project (i.e. `codecs`). Each library is built as it's own individual DocFx site and it's xref maps are exported to file to be shared between DocFx builds.
- - `docfx.global.json` - Each library DocFx json references this file for global metadata. This is where all global metadata such as Title, Logo, Footer, etc... are declared.
- - `docfx.global.subsite.json` - Each library DocFx json references this file for global metadata which denotes the [`_rel`](https://dotnet.github.io/docfx/tutorial/intro_template.html#system-generated-properties) (The relative path of the root output folder from current output file. i.e. the base URL). For example: `https://lucenenet.apache.org/docs/4.8.0-beta00009/`.
+ - `docfx.{library}.json` - Where {library} is an individual Lucene.NET project (i.e. `codecs`). Each library is built as its own individual DocFx site and it's xref maps are exported to file to be shared between DocFx builds.
+ - `docfx.global.json` - Each library DocFx JSON references this file for global metadata. This is where all global metadata such as Title, Logo, Footer, etc... are declared.
+ - `docfx.global.subsite.json` - Each library DocFx JSON references this file for global metadata which denotes the [`_rel`](https://dotnet.github.io/docfx/tutorial/intro_template.html#system-generated-properties) (The relative path of the root output folder from current output file. i.e. the base URL). For example: `https://lucenenet.apache.org/docs/4.8.0-beta00009/`.
- `docfx.site.json` - Once each library is built and it's xref maps are exported, the main documentation site container is built with this definition.
- `lucenetemplate/*` - The custom template files to style the website
- `*.md` - The root site content such as the index and download pages
@@ -132,7 +132,7 @@ Where `<LUCENE DIRECTORY>` is the `lucene` sub folder location of the Java Lucen
#### Automated execution
-A powershell script has been created to automate the above. Execute the `./src/docs/convert.ps1` script and enter the current Lucene version to convert from. For example, for Lucene.Net 4.8.0 we are converting from the Java Lucene build release of ["4.8.1"](https://github.com/apache/lucene-solr/releases/tag/releases%2Flucene-solr%2F4.8.1) so in this case enter: 4.8.1 at the prompt or call the whole script like `./src/docs/convert.ps1 -JavaLuceneVersion 4.8.1`
+A PowerShell script has been created to automate the above. Execute the `./src/docs/convert.ps1` script and enter the current Lucene version to convert from. For example, for Lucene.Net 4.8.0 we are converting from the Java Lucene build release of ["4.8.1"](https://github.com/apache/lucene-solr/releases/tag/releases%2Flucene-solr%2F4.8.1) so in this case enter: 4.8.1 at the prompt or call the whole script like `./src/docs/convert.ps1 -JavaLuceneVersion 4.8.1`
#### Review, commit and merge
diff --git a/websites/site/contributing/make-release.md b/websites/site/contributing/make-release.md
index bfe02f86d..460a03cd1 100644
--- a/websites/site/contributing/make-release.md
+++ b/websites/site/contributing/make-release.md
@@ -279,7 +279,7 @@ Please review the Apache Release Policy to understand the requirements for evalu
https://www.apache.org/legal/release-policy.html
Please vote on releasing these packages as Apache Lucene.NET [version]. The vote is open for at least the next 72 hours, i.e. midnight UTC on [YYYY-MM-DD]
-http://www.timeanddate.com/counters/customcounter.html?year=[YYYY]&month=[MM]&day=[DD]
+https://www.timeanddate.com/counters/customcounter.html?year=[YYYY]&month=[MM]&day=[DD]
diff --git a/websites/site/contributing/source.md b/websites/site/contributing/source.md
index cc4d44209..b2dbebac5 100644
--- a/websites/site/contributing/source.md
+++ b/websites/site/contributing/source.md
@@ -33,7 +33,7 @@ However, it's common for developers to build and test the project using Visual S
Once the solution has been opened in Visual Studio you can build it as you would any solution by selecting "Build Solution" from the "Build" menu. Likewise you can run the unit tests for the solution just like you would for any other solution by selecting "Run All Tests" from the "Tests" menu.
-This is a large solution with more than [644K+ lines](https://lucenenet.apache.org/images/contributing/source/lucenenet-repo-lines-of-code--jan-2022.png) of code so it may take a bit longer for Visual Studio to perform these operations then you are use to but it should display progress information while it does it work.
+This is a large solution with more than [644K+ lines](https://lucenenet.apache.org/images/contributing/source/lucenenet-repo-lines-of-code--jan-2022.png) of code so it may take a bit longer for Visual Studio to perform these operations then you are used to but it should display progress information while it does it work.
## Making Changes
diff --git a/websites/site/contributing/versioning.md b/websites/site/contributing/versioning.md
index bb1d38ed2..5a07777c8 100644
--- a/websites/site/contributing/versioning.md
+++ b/websites/site/contributing/versioning.md
@@ -18,7 +18,7 @@ The version number that is used in the build process is called the _Package Vers
- Pre-Release (i.e. `4.8.0-beta00001`)
- Production Release (i.e. `4.8.0`)
- - Production Release Patch N (i.e where N is 1, `4.8.0.1`, where N is 2, `4.8.0.2`, etc)
+ - Production Release Patch N (i.e. where N is 1, `4.8.0.1`, where N is 2, `4.8.0.2`, etc.)
- Version numbers correspond to GitHub milestones, so when releasing a milestone, the same version number should be used
diff --git a/websites/site/release-notes/version-4.8.0-beta00016.md b/websites/site/release-notes/version-4.8.0-beta00016.md
index 140fa29b5..fb86560f8 100644
--- a/websites/site/release-notes/version-4.8.0-beta00016.md
+++ b/websites/site/release-notes/version-4.8.0-beta00016.md
@@ -76,7 +76,7 @@ It is recommended that all .NET Framework users migrate as soon as possible.
### Bugs
* [#363](https://github.com/apache/lucenenet/pull/363), [#534](https://github.com/apache/lucenenet/pull/534) - `Lucene.Net.Replicator.Http.HttpReplicatorTest::TestBasic()`. This was failing intermittently due to the Timeout value being set to 1 second instead of the 60 second value that was used in Java. It has been increased to the .NET default of 100 seconds.
-* [#363](https://github.com/apache/lucenenet/pull/363), [#534](https://github.com/apache/lucenenet/pull/534) - `Lucene.Net.Replicator.IndexAndTaxonomyReplicationClientTest::TestConsistencyOnExceptions()` and `Lucene.Net.Replicator.IndexReplicationClientTest::TestConsistencyOnExceptions()` were failing due to to exceptions being raised on the worker thread and missing locks, which have both been addressed.
+* [#363](https://github.com/apache/lucenenet/pull/363), [#534](https://github.com/apache/lucenenet/pull/534) - `Lucene.Net.Replicator.IndexAndTaxonomyReplicationClientTest::TestConsistencyOnExceptions()` and `Lucene.Net.Replicator.IndexReplicationClientTest::TestConsistencyOnExceptions()` were failing due to exceptions being raised on the worker thread and missing locks, which have both been addressed.
* [#535](https://github.com/apache/lucenenet/pull/535) - Added `[SuppressCodecs]` attribute where required for custom Lucene.NET tests
* [#536](https://github.com/apache/lucenenet/pull/536) - Modified all `TermsEnum.MoveNext()` methods to return a check for `null` rather than returning `true`
* [#537](https://github.com/apache/lucenenet/pull/537) - `Lucene.Net.TestFramework.Index.BasePostingsFormatTestCase`: Removed `IndexOptions.NONE` from the list of available options, since it is not a valid test option