docs(v2): Fix url bugs in v2 docs (#3534)

* Fix broken link in the documentation

* Fix broken url caused by typo

* Fix broken link caused by typo

website-1.x/docs/guides-search.md

@@ -26,7 +26,7 @@ const siteConfig = {
 
 ## Extra Search Options
 
-You can also specify extra [search options used by Algolia](https://community.algolia.com/docsearch/documentation/) by using an `algoliaOptions` field in `algolia`. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be [found here](https://www.algolia.com/doc/api-reference/api-parameters/#overview).
+You can also specify extra [search options used by Algolia](https://docsearch.algolia.com/) by using an `algoliaOptions` field in `algolia`. This may be useful if you want to provide different search results for the different versions or languages of your docs. Any occurrences of "VERSION" or "LANGUAGE" will be replaced by the version or language of the current page, respectively. More details about search options can be [found here](https://www.algolia.com/doc/api-reference/api-parameters/#overview).
 
 ```js
 const siteConfig = {
@@ -40,7 +40,7 @@ const siteConfig = {
 };
 ```
 
-Algolia might provide you with [extra search options](https://community.algolia.com/docsearch/documentation/). If so, you should add them to the `algoliaOptions` object.
+Algolia might provide you with [extra search options](https://docsearch.algolia.com/). If so, you should add them to the `algoliaOptions` object.
 
 ## Controlling the Location of the Search Bar
 

website/docs/api/docusaurus.config.js.md

@@ -308,7 +308,7 @@ module.exports = {
 
 ### `ssrTemplate`
 
-An HTML template written in [Eta's syntax](https://eta.js.org/docs/syntax/overview) that will be used to render your application. This can be used to set custom attributes on the `body` tags, additional `meta` tags, customize the `viewport`, etc. Please note that Docusaurus will rely on the template to be correctly structured in order to function properly, once you do customize it, you will have to make sure that your template is compliant with the requirements from `upstream`.
+An HTML template written in [Eta's syntax](https://eta.js.org/docs/syntax#syntax-overview) that will be used to render your application. This can be used to set custom attributes on the `body` tags, additional `meta` tags, customize the `viewport`, etc. Please note that Docusaurus will rely on the template to be correctly structured in order to function properly, once you do customize it, you will have to make sure that your template is compliant with the requirements from `upstream`.
 
 - Type: `string`
 

website/docs/deployment.md

@@ -11,7 +11,7 @@ npm run build
 
 Once it finishes, the static files will be generated within the `build/` directory.
 
-You can deploy your site to static site hosting services such as [Vercel](https://vercel.com/), [GitHub Pages](https://pages.github.com/), [Netlify](https://www.netlify.com/), [Render](https://render.com/static-sites), and [Surge](https://surge.sh/help/getting-started-with-surge). Docusaurus sites are statically rendered so they work without JavaScript too!
+You can deploy your site to static site hosting services such as [Vercel](https://vercel.com/), [GitHub Pages](https://pages.github.com/), [Netlify](https://www.netlify.com/), [Render](https://render.com/docs/static-sites), and [Surge](https://surge.sh/help/getting-started-with-surge). Docusaurus sites are statically rendered so they work without JavaScript too!
 
 ## Testing Build Local