Update some old links (#1287)

Signed-off-by: Tatsuya Sato <[email protected]>

.github/settings.yml

@@ -1,7 +1,7 @@
 repository:
   name: fabric-samples
   description: Samples for Hyperledger Fabric
-  homepage: https://wiki.hyperledger.org/display/fabric
+  homepage: https://lf-hyperledger.atlassian.net/wiki/spaces/fabric
   default_branch: main
   has_downloads: true
   has_issues: true

CODEOWNERS

@@ -1,4 +1,4 @@
 # SPDX-License-Identifier: Apache-2.0
 
-# Fabric Samples Maintaners
+# Fabric Samples Maintainers
 *	@hyperledger/fabric-samples-maintainers

CODE_OF_CONDUCT.md

@@ -2,7 +2,7 @@ Code of Conduct Guidelines
 ==========================
 
 Please review the Hyperledger [Code of
-Conduct](https://wiki.hyperledger.org/community/hyperledger-project-code-of-conduct)
+Conduct](https://lf-hyperledger.atlassian.net/wiki/spaces/HYP/pages/19595281/Hyperledger+Code+of+Conduct)
 before participating. It is important that we keep things civil.
 
 <a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>.

SECURITY.md

@@ -6,7 +6,6 @@ If you think you have discovered a security issue in any of the Hyperledger proj
 
 There are two ways to report a security bug. The easiest is to email a description of the flaw and any related information (e.g. reproduction steps, version) to [security at hyperledger dot org](mailto:[email protected]).
 
-The other way is to file a confidential security bug in our [JIRA bug tracking system](https://jira.hyperledger.org). Be sure to set the "Security Level" to "Security issue".
-
-The process by which the Hyperledger Security Team handles security bugs is documented further in our [Defect Response page](https://wiki.hyperledger.org/display/SEC/Defect+Response) on our [wiki](https://wiki.hyperledger.org).
+The other way is to file a confidential security bug in the repository's [security advisories page](https://github.com/hyperledger/fabric/security/advisories). Guidance can be found in the GitHub documentation on [privately reporting a security vulnerability](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability).
 
+The process by which the Hyperledger Security Team handles security bugs is documented further in our [Defect Response page](https://lf-hyperledger.atlassian.net/wiki/spaces/SEC/pages/20283618/Defect+Response) on our [wiki](https://lf-hyperledger.atlassian.net/wiki).